Skip to content
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

add support for --tag #4

Open
ghost opened this issue Mar 23, 2015 · 3 comments
Open

add support for --tag #4

ghost opened this issue Mar 23, 2015 · 3 comments

Comments

@ghost
Copy link

ghost commented Mar 23, 2015

from npm help publish:

[--tag  <tag>]  Registers  the  published package with the given tag,
         such that npm install <name>@<tag> will  install  this  version.   By
         default, npm publish updates and npm install installs the latest tag.

I would like to see this support added to publish so that I can have a CI build publish a "beta" version of my software.

Unfortunately, it looks like the npm publish api may not support this ...

@ghost
Copy link
Author

ghost commented Mar 23, 2015

maybe using publish config is required?

@ghost
Copy link
Author

ghost commented Mar 24, 2015

I've submitted a pull request to add --tag support ...

but I've also implemented the following in my CI to get what I want:

NPM_CONFIG_TAG=beta npm test

(my package has a "posttest" script that calls publish)

possibly, it's better just to document that usage instead of writing more code

@seanpk
Copy link
Contributor

seanpk commented Apr 12, 2016

--tag support isn't really working ... it checks the tag for the remote version, but when it publishes, it doesn't tag the release with that tag.
... I've got a PR coming

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant