ci: use CI App token for release-please#170
Merged
Merged
Conversation
Source release-please-action's token from the softleader CI App (actions/create-github-app-token@v3) instead of the default GITHUB_TOKEN, matching bump-spring. GITHUB_TOKEN-produced events don't trigger workflows, so a future on-release / on-push-tags listener wouldn't fire on a release. The App token re-enables those events, fixes the autorelease label quirk, and lets commitlint lint the release PR. No recursion risk: the release PR is human-merged and release-please's own commits land on the release-please-- side branch. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@softleader.com.tw>
shihyuho
force-pushed
the
ci/release-please-app-token
branch
from
2af462a to
df3d003
Compare
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.
What
Source release-please-action's token from the softleader CI App (actions/create-github-app-token@v3) instead of the default GITHUB_TOKEN.
Why
GITHUB_TOKEN-produced events don't trigger other workflows (GitHub recursion guard), so a future on-release / on-push-tags listener wouldn't fire on a release-please release. The CI App is already wired in this repo (bump-spring.yml uses it). It also fixes the known autorelease label quirk and lets commitlint lint the release PR (the chore(main): release title is conventional-valid).
No recursion risk: the release PR is human-merged and release-please's own commits land on the release-please-- side branch, so it never self-triggers.
Behavior changes