RFC: Publish set the tag accordingly to the semver version number #317
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.
Currently : Versions numbers have no direct connection with dist-tags.
It should be possible to run
npm publish
without specifying the--tag
argument, instead it will pick the tag based on the semver version number (insidepackage.json
).Examples of various versions values inside
package.json
16.0.3
release the package attached to thelatest
tag16.0.3-tagname.1
release the package attached to thetagname
tag16.0.3-beta.1
release the package attached to thebeta
tagReferences
npm/feedback
: npm publish and tag releases feedback#194yarnpkg
about the same feature : [Feature] yarn npm publish set the tag accordingly to the version number yarnpkg/berry#2444latest
tag discussion : Mutability of the `latest` tag feedback#109