ci: use dedicated release App token to publish releases - #28553
Merged
Conversation
The Publish release step runs gh release create, which creates the v$version tag in addition to the release. The active tag-create protection ruleset blocks github-actions[bot] (the default GITHUB_TOKEN), producing HTTP 403: Resource not accessible by integration. Mint an installation token from a dedicated release GitHub App (RELEASE_APP_ID / RELEASE_APP_PRIVATE_KEY) and use it only for the Publish release step. The App is added to the ruleset bypass list as an Integration actor. Refs coder/security-automation#297
Contributor
Author
|
Created the custom app and set |
mtojek
approved these changes
Aug 25, 2026
mtojek
left a comment
Member
There was a problem hiding this comment.
Great job, Jakub! Let's backport this to v2.35, and see if it helps 👍 If so, then backport to v2.36.
This was referenced 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.
Problem
The
Publish releasestep fails withHTTP 403: Resource not accessible by integrationbecause the defaultGITHUB_TOKENcannot create the release tag under the active tag-create protection ruleset.Change
Use a dedicated GitHub App token for the
Publish releasestep:Generate release App tokenstep usingsecrets.RELEASE_APP_ID/secrets.RELEASE_APP_PRIVATE_KEY.GITHUB_TOKENto the minted App token.Required before merge (admin)
coder/coder.RELEASE_APP_ID/RELEASE_APP_PRIVATE_KEY.Refs coder/security-automation#297.