Set package version from release tag before publishing#381
Closed
carlostxm wants to merge 1 commit into
Closed
Conversation
The previous workflow relied on package.json having the correct version, but these repos don't bump it manually before releases. Co-authored-by: Cursor <cursoragent@cursor.com>
carlostxm
force-pushed
the
fix/npm-publish-version
branch
from
73aa9b8 to
2fba7bc
Compare
Contributor
Author
|
Not needed — version is bumped locally before creating the release. |
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.
Adds
npm versionstep to set the version from the git tag beforenpm publish, so we don't need to manually bump package.json.Made with Cursor