fix: use PAT for release-please to trigger publish workflow#86
Merged
rogeriochaves merged 1 commit intomainfrom Feb 22, 2026
Merged
fix: use PAT for release-please to trigger publish workflow#86rogeriochaves merged 1 commit intomainfrom
rogeriochaves merged 1 commit intomainfrom
Conversation
The default GITHUB_TOKEN does not trigger downstream workflows when release-please creates a GitHub Release. Use a PAT (RELEASE_PLEASE_TOKEN) so the release:published event fires and triggers the publish workflow naturally. Also remove the now-unnecessary workflow_call workaround.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
RELEASE_PLEASE_TOKENPAT instead of defaultGITHUB_TOKENfor release-please, so that created GitHub Releases trigger therelease: publishedevent for the publish workflowtrigger-publishanddebug-outputsworkaround jobs from release-please.ymlworkflow_calltrigger from publish.yml (no longer needed)This is the same fix applied to the scenario repo. The default
GITHUB_TOKENis a GitHub limitation — events created by it don't trigger other workflows.Prerequisites
RELEASE_PLEASE_TOKENsecret is set in the repo settings (a GitHub PAT withcontents: writeandpull-requests: writepermissions)Test plan