This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
doc/tag: candidate explanation of tag workflow #6849
Closed
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
| @@ -23,6 +23,27 @@ This also applies to `npm dedupe`. | |||
|
|
|||
| Publishing a package always sets the "latest" tag to the published version. | |||
|
|
|||
| ## PURPOSE | |||
|
|
|||
| Tags can be used to provide an alias or indirection over version numbers. For example, `npm` currently uses | |||
There was a problem hiding this comment.
"alias or indirection over" → "alias instead of"? (Including both of alias and indirection is significantly less clear than either one on its own.)
|
Overall, a useful set of clarifications. I left some comments, but overall this LGTM, so once you decided you're satisfied with this, let me know and I'll merge. |
|
I am happy with this. Do you want it squashed? |
incorporate line notes typo: namenspace
smikes
force-pushed
the
6846-npm-tag-doc
branch
from
7dbd983
to
77f0e71
Compare
|
Rebased and squashed. |
|
Rebased (again) but otherwise landed as-is as 17f66ce. Thanks! Don't freeze! ❄️ |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Some suggestions re: tag workflow. Open to major revision/bikeshedding.
There is a distinction between 'tag' (eg a git tag) which identifies a specific release (and is very closely related to 'version') and 'dist-tag' which identifies both a stream of releases and the most current version in that release, but I am having a hard time articulating it.
Is the name "tag" or "dist-tag" still open to bikeshedding or is it basically set in stone?