ci: use App token in In-case-of-failure rollback job#20162
Merged
Conversation
The rollback job deletes the release git tag when the pipeline fails mid-way. Previously it used the implicit GITHUB_TOKEN which lacks the `workflows` scope — so tag deletion would fail with "workflows scope may be required" if the tag pointed to a workflow-touching commit. Apply the same App token pattern as build-release: generate a token via RELEASE_BOT before checkout so that git push -d uses the App's credentials, which carry Workflows:Write permission. Co-Authored-By: Claude
yperbasis
approved these changes
Mar 26, 2026
yperbasis
pushed a commit
that referenced
this pull request
Mar 26, 2026
…lback (#20164) Cherry-pick of #20157 and #20162 to `release/3.3`. ## Summary - `build-release`: use GitHub App token for checkout so `git push` of the release tag has `workflows` scope (#20157) - `In-case-of-failure`: same App token treatment for the rollback `git push -d` that deletes the tag on failure (#20162) Both fixes require `RELEASE_BOT` App to have `Workflows: Write` permission (already granted). Co-Authored-By: Claude
yperbasis
pushed a commit
that referenced
this pull request
Mar 26, 2026
…lback (#20165) Cherry-pick of #20157 and #20162 to `release/3.4`. ## Summary - `build-release`: use GitHub App token for checkout so `git push` of the release tag has `workflows` scope (#20157) - `In-case-of-failure`: same App token treatment for the rollback `git push -d` that deletes the tag on failure (#20162) Both fixes require `RELEASE_BOT` App to have `Workflows: Write` permission (already granted). Co-Authored-By: Claude
awskii
approved these changes
Mar 26, 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Summary
In-case-of-failurerollback job deletes the release git tag when the pipeline fails mid-way (after the tag was pushed but before the release completed)GITHUB_TOKEN, which lacks theworkflowsscope — tag deletion would fail with "workflows scope may be required" if the tag pointed to a workflow-touching commitbuild-release: generate a token viaRELEASE_BOTbefore checkout sogit push -duses the App's credentials (which carryWorkflows: Write)Test plan
In-case-of-failurejob picks up the App token on next release run🤖 Generated with Claude