Fix drop-release auth to use git config extraheader — Closes #129#130
Merged
conradbzura merged 1 commit intowool-labs:masterfrom Mar 27, 2026
Merged
Conversation
The drop-release step was authenticating via git remote set-url with an embedded token, which fails for GitHub App tokens. Switch to the git config http.extraheader approach that cut-release already uses successfully.
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.
Summary
Replace the
git remote set-urlauthentication in thedrop-releasejob with thegit config --local http.extraheaderapproach thatcut-release.yamlalready uses successfully. Thedrop-releasestep was failing to authenticate when deleting the release branch, and this may fix it.Closes #129
Proposed changes
Switch drop-release auth method (
publish-release.yaml)The
drop-releasejob authenticated by embedding the app token in the remote URL viagit remote set-url, which was failing. Replace it withgit config --local http.extraheader, which sets anAUTHORIZATIONheader with a base64-encoded token — the same approach used incut-release.yaml:71.Before:
git remote set-url origin "https://x-access-token:${GH_TOKEN}@github.com/${REPO}.git"After: