fix(release-notes): don't persist credentials on release-foundry checkout#58
Merged
Merged
Conversation
…kout The post-job "Removing auth" cleanup for this read-only checkout fails with exit 128 (git refuses to operate on the repo by job-end, e.g. due to ownership changes from the subsequent go build/setup-go steps). Since this checkout is only used to build the rf binary and never pushes back, skipping credential persistence avoids the cleanup path entirely. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
nirmal-bluefunda
approved these changes
Jun 8, 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
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.
Summary
Check out release-foundrystep ingithub-release-notes.ymlchecks out a read-only copy of release-foundry just to build therfbinary — it never pushes back.actions/checkout's post-job "Removing auth" cleanup was failing with exit code 128 (git refuses to operate on the repo by job-end, likely due to ownership changes from the subsequentsetup-go/go buildsteps), marking otherwise-successful jobs as failed.persist-credentials: falseskips writing the temporaryhttp.extraheaderauth config in the first place, so there's nothing for the post-step cleanup to remove and the failure path is avoided entirely.Test plan
GitHub Release Notesreusable workflow (e.g. via a release in a calling repo) and confirm the job completes without theRemoving auth/ exit code 128 failure🤖 Generated with Claude Code