fix: allow same version in npm publish workflow#2
Merged
lmcmz merged 3 commits intoOutblock:mainfrom Feb 11, 2026
Merged
Conversation
The version extraction now correctly handles both `v1.0.0` and `1.0.0` tag formats. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…rkflow" This reverts commit fecdc0f.
Add --allow-same-version flag to prevent failure when package.json already has the same version as the release tag. Co-Authored-By: Claude Opus 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
--allow-same-versionflag tonpm versionin release workflow to prevent failure whenpackage.jsonalready matches the release tag versionContext
The
npm-publishjob fails with "Version not changed" when the tag version matches the existingpackage.jsonversion (e.g. both are1.0.0).🤖 Generated with Claude Code