Publish to the latest dist tag [skip ci] #6738
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 is because with scoped packages the `latest` package was the first publish we did - This happens to be beta.4.. - So in this case we should publish whatever version as latest anyway
hzoo
added
the
PR: Internal 🏠
|
makes sense |
|
merge whenever, mostly just fyi |
existentialism
approved these changes
Nov 3, 2017
|
Sounds fine to me. Should we consider adding a message to the READMEs of babel-core and such saying it's still a Beta, since the READMEs on npm will get pulled from the |
|
Yeah we can do that |
lock
bot
added
the
outdated
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.
latestpackage was the first publish we didAnd I manually have to do
npm dist-tag add @babel/cli@7.0.0-beta.31 latestnow for all pkgs