Skip to content

ci: Fix keep-node-current push (duplicate Authorization header) - #1356

Merged
TimothyJones merged 1 commit into
mainfrom
fix/keep-node-current-push-auth
Jul 18, 2026
Merged

ci: Fix keep-node-current push (duplicate Authorization header)#1356
TimothyJones merged 1 commit into
mainfrom
fix/keep-node-current-push-auth

Conversation

@TimothyJones

Copy link
Copy Markdown
Member

The manually-dispatched run confirmed the action's logic works (it planned: drop Node 20, add Node 26), but the git push failed:

##[error]git push --force origin chore/node-version-sync failed (exit 128):
         remote: Duplicate header: "Authorization"
fatal: ... The requested URL returned error: 400

actions/checkout persists a credential (http.extraheader Authorization) in the git config by default. When the action then pushes with its own token, git sends two Authorization headers and GitHub returns 400.

Fix: set persist-credentials: false on the checkout step so only the action's token is used — the same pattern already used in scorecard.yml.

🤖 Generated with Claude Code

The dispatched run failed at git push with 'Duplicate header:
Authorization' (remote 400). actions/checkout persists a credential
extraheader by default; combined with the action's own push token,
git sends two Authorization headers. Disable persist-credentials so
only the action's token is used, matching scorecard.yml.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@TimothyJones
TimothyJones enabled auto-merge (squash) July 18, 2026 09:03
@TimothyJones
TimothyJones merged commit 848b226 into main Jul 18, 2026
14 checks passed
@TimothyJones
TimothyJones deleted the fix/keep-node-current-push-auth branch July 18, 2026 09:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant