-
Notifications
You must be signed in to change notification settings - Fork 798
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recommend using --tag argument for prerelease in readme instructions #183
Comments
We have |
👍 cool, I think I can knock that out later tonight! |
stevemao
pushed a commit
that referenced
this issue
Aug 8, 2017
The `--tag` argument to npm publish allows you to publish a prerelease without the prerelease assuming the 'latest' tag and causing users to download the prerelease by default. Instead, we recommend `--tag prerelease` by default when `--prerelease` is set in the `standard-version` call, so to install a prerelease version of the module, users will install `module@foo` or specify the exact version of the prerelease version. Fixes #183
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Nothing this post from Mike Bostock, as well as the current behavior of npm, would it be preferable for standard-version to say
Instead of always
Which causes prerelease releases like 3.1.0-alpha.0 to be installed instead of stable releases?
The text was updated successfully, but these errors were encountered: