Publish to npm on version bump instead of tag push#27
Merged
Conversation
Removes the requirement to manually push a v* tag to trigger a release. Now publishes automatically when package.json version changes on master. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
2 participants
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
v*tag trigger with a push-to-master trigger (filtered topackage.jsonchanges)jqto compareHEAD~1vs currentpackage.jsonversionchanged == 'true', so only actual version bumps trigger a publishHow to release going forward
Just bump the version in
package.jsonand merge tomaster— no manual tagging required.Test plan
package.jsonversion → workflow should run and publish to npmpackage.jsonversion → workflow should not trigger (paths filter)🤖 Generated with Claude Code