fix update releases workflow#237
Merged
Merged
Conversation
PR SummaryMedium Risk Overview Backfills the missing Reviewed by Cursor Bugbot for commit 66a7743. Bugbot is set up for automated code reviews on this repo. Configure here. |
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
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
This fixes the
update-releasesworkflow path that failed after theforc-wallet v0.16.4release and backfills the missingreleases.tomlentry that the failed automation never landed.Root cause
The failing run was the
Update releases.tomljob in CI run24651220002.actions/checkout@v6persisted an auth header in the release-tag checkout, andpeter-evans/create-pull-requestadded another one when it prepared the PR branch. Duringgit remote prune origin, GitHub rejected the request with400 Duplicate header: "Authorization", so the final PR-creation step failed even though the release metadata update itself succeeded.Changes
persist-credentials: falseon theCheckout release tagstep in.github/workflows/ci.ymlpeter-evans/create-pull-requestfromv6tov8forc-wallet 0.16.4entry toreleases.tomlImpact
Future release runs should be able to create the follow-up
releases.tomlPR without tripping over duplicate GitHub auth headers, andmainregains the missing compatibility metadata forforc-wallet 0.16.4.Validation
git diff --check origin/main...HEAD24651220002and matched the workflow fix to the observedDuplicate header: "Authorization"error