ci: use the org-wide exadev App token for the release-commit push - #10
Merged
Merged
Conversation
main's ruleset now requires every change to land via a pull request, which blocks @semantic-release/git's own direct push of the version-bump commit -- the default GITHUB_TOKEN has no bypass for that rule. Generates an installation token from the exadev GitHub App (already installed with access to every ExaDev repo, and added as an Integration bypass_actor on this repo's ruleset) and uses it for checkout's git credentials instead, so only the push itself is elevated; every other API call in the job keeps using GITHUB_TOKEN unchanged.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
🎉 This PR is included in version 1.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Main went red immediately after the new branch-protection ruleset started requiring pull requests: semantic-release's own direct push of the version-bump commit (via @semantic-release/git) got rejected with GH013, since the default GITHUB_TOKEN has no bypass for that rule.
Fix: generate an installation token from the exadev GitHub App (org-wide access, already added as an Integration bypass_actor on this repo's ruleset) and use it for checkout's git credentials, so the release push authenticates as an actor the ruleset explicitly allows through. Every other step in the job keeps using the plain GITHUB_TOKEN, unchanged.
Verified: the exadev app's installation has
contents: write, and I confirmed via a disposable probe workflow (pushed and deleted) thatsecrets.GH_APP_ID/secrets.GH_APP_PRIVATE_KEYdo resolve to this app before relying on it here.