Harden release tag creation with retry - #42
Merged
Conversation
Wrap the gh api git/refs tag-creation call in a 2-3 attempt retry loop to tolerate transient "403 Resource not accessible by integration" errors caused by GitHub App token propagation lag. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Code Coverage |
Test Results60 tests 60 ✅ 0s ⏱️ Results for commit cd1bb45. |
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.
The release job's Create git tag step calls
gh api .../git/refs -X POSTand intermittently fails with403 Resource not accessible by integrationdue to transient GitHub App token propagation lag. This wraps the single gh api call in a minimal 3-attempt retry/backoff loop (5s, 10s). No other steps or jobs changed; the release job only runs on push to main so it does not execute on this PR.