Open
Conversation
- Trigger on push to main (not just manual workflow_dispatch) - Commit version bump back to repo so package.json stays in sync - Add [skip ci] guard to prevent infinite loop from the version bump commit - Fix script name: publish:npm → publish --non-interactive Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Problem
The publish workflow was
workflow_dispatchonly (manual trigger), which meant someone had to remember to go to GitHub Actions and click run after every merge. The programmer was working around this by publishing locally instead.Changes
main(plus keepworkflow_dispatchas manual fallback)--no-git-tag-versionchangedpackage.jsononly in the CI runner, so the repo's version was always behind npm. Now the bumpedpackage.jsonis committed and pushed with[skip ci]to prevent an infinite loopyarn publish:npmdoesn't exist; changed toyarn publish --non-interactive(matches thepublishscript inpackage.json)Result
After merging any PR into
main, the workflow runs automatically, bumps the patch version, commits it, and publishes to npmjs.com. No manual steps needed.🤖 Generated with Claude Code