ci(release-please): authenticate with the org's release-please App - #2
Merged
Conversation
This is the repo template, so every repository created from it inherits this. Also bumps release-please-action to v5.0.0 (matching what the org actually runs) and flags release-type as the one line a new repo must set.
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.
This is the repo template, so this is the highest-leverage of the set: every repository created from it inherits this config, and new repos stop being born needing a PAT.
release-please-managerApp (vars.RP_APP_ID+secrets.RP_APP_PRIVATE_KEY, both org-level and visible to all repositories) instead of a personal access token. The App token is minted per run, expires in an hour, and belongs to the org rather than to whoever created the PAT.actions: writeon the App is what makes release-please's tags trigger downstream release workflows — the defaultGITHUB_TOKENdeliberately does not.release-please-actionv4.4.0 → v5.0.0, matching what the rest of the org runs.release-typeas the one line a new repo must change.Falls back to
RELEASE_PLEASE_PATand warns via an annotation if the App is ever unavailable, so it degrades visibly rather than silently.🤖 Generated with Claude Code