Repository navigation
fix(publish): accept GitHub squash merge titles - #242
Merged
Merged
Conversation
John-David Dalton (jdalton)
had a problem deploying
to
publish-npm
October 19, 2026 02:28 — with 
GitHub Actions
Failure
GitHub Actions
Failure
This branch had an error being deployed
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.
Note
Low Risk
Small CI guard change in the npm publish workflow; it only relaxes subject-line matching for squash-merge titles during reserved resume validation.
Overview
Reserved publish resume no longer fails when the version-bump commit on the default branch has a GitHub squash-merge title (e.g.
chore: bump version to X.Y.Z (#123)).In the Validate reserved release resume step of
publish-npm.yml, the workflow still finds the bump commit via--grep, but strips a trailing(#<PR>)suffix from the commit subject before comparing it to the exact stringchore: bump version to $VERSION. That letsresume-publishsucceed after squash-merging the release PR without weakening the other ancestry and checkout checks.Reviewed by Cursor Bugbot for commit ecf7472. Configure here.