fix!: publishing prerelease requires explicit tag #7910
Merged
Conversation
This file contains 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
|
this does not implement rfc 7 |
|
maybe check should go on line 125 after tarball pack Line 125 in 9ca373a |
|
or within |
wraithgar
changed the title
wraithgar
previously approved these changes
Nov 25, 2024
reggi
force-pushed
the
reggi/abort-no-prerelease-tag
branch
2 times, most recently
from
55d74be
to
3a43aa5
Compare
reggi
force-pushed
the
reggi/abort-no-prerelease-tag
branch
from
3a43aa5
to
03b8d32
Compare
wraithgar
approved these changes
Nov 25, 2024
This was referenced Dec 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
BREAKING CHANGE: When publishing a package with a pre-release version, you must explicitly specify a tag.
ref: npm/statusboard#898