{{ message }}
ci: use dedicated release App token to publish releases (backport 2.34) [ESR] - #28590
Merged
Merged
Conversation
## Problem The `Publish release` step fails with `HTTP 403: Resource not accessible by integration` because the default `GITHUB_TOKEN` cannot create the release tag under the active tag-create protection ruleset. ## Change Use a dedicated GitHub App token for the `Publish release` step: - Add a `Generate release App token` step using `secrets.RELEASE_APP_ID` / `secrets.RELEASE_APP_PRIVATE_KEY`. - Switch only that step's `GITHUB_TOKEN` to the minted App token. ## Required before merge (admin) 1. Create the release GitHub App (least privilege) and install it on `coder/coder`. 2. Configure `RELEASE_APP_ID` / `RELEASE_APP_PRIVATE_KEY`. 3. Add the App to the tag-create protection ruleset bypass list. Refs coder/security-automation#297.
Contributor
mtojek
self-requested a review
August 25, 2026 18:18
mtojek
approved these changes
Aug 25, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Backport of #28553 to
release/2.34.Use a dedicated GitHub App token (
secrets.RELEASE_APP_ID/secrets.RELEASE_APP_PRIVATE_KEY) for thePublish releasestep instead of the defaultGITHUB_TOKEN.gh release createtargets a release-branch commit that modifies files under.github/workflows/relative to the default branch. The create-release API requires the authenticating token to be authorized to modify workflows; the defaultGITHUB_TOKENis not, so it fails withHTTP 403: Resource not accessible by integration. Thecoder-release-publisherApp token has code + workflows write.Requires
RELEASE_APP_ID/RELEASE_APP_PRIVATE_KEYto be configured (already set oncoder/coder).Refs coder/security-automation#297.