Repository navigation
fix(ci): scoop/cask manifest PR fails after every release - #33
Merged
Merged
Conversation
v5 (Node 20, forced to Node 24) sends a duplicate Authorization header on push and fails with HTTP 400, so the scoop/cask manifest PR is never opened after a release. v7 handles runner credentials correctly. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
kolah
approved these changes
Sep 18, 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
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.
After a release publishes, the "Update scoop manifests" job is supposed to open a PR bumping the Scoop and Cask package versions. It has been failing at the PR-creation step, so those manifests never get updated automatically (seen on the 2.24.0 release). The release binaries themselves are unaffected.
The step used an old version of the create-pull-request action that GitHub's current runners no longer support: it sends the login credential twice when pushing, and the push is rejected. Moving to the current version fixes it. Also pinned the checkout action to a fixed version instead of tracking its moving branch.
After this merges, the 2.24.0 manifest bump can be produced by re-running the release job (or the next release will do it automatically).
🤖 Generated with Claude Code