This repository has been archived by the owner. It is now read-only.

RF: release channels #2718

Closed
vojtajina opened this Issue Aug 14, 2012 · 2 comments

Comments

Projects
None yet
2 participants
@vojtajina

I think it might be helpful to have multiple release channels.

You can already achieve it by:

npm publish // publishing new v1.0.1
npm tag some@1.0.0 latest
npm tag some@1.0.1 canary

Then people can install canary release by:

npm install -g some@canary

I think it might be helpful to have better support for this scenario:

  • add argument to publish (which channel, the default would be latest)
  • display available channels on npmjs.org package info
  • installing some@canary would mean, that npm update keeps updating from canary channel
@isaacs

This comment has been minimized.

Show comment
Hide comment
@isaacs

isaacs Aug 15, 2012

Member

That already works, exactly how you describe it.

Member

isaacs commented Aug 15, 2012

That already works, exactly how you describe it.

@isaacs isaacs closed this Aug 15, 2012

@isaacs

This comment has been minimized.

Show comment
Hide comment
@isaacs

isaacs Aug 15, 2012

Member

Also, you can do it in one step, if you like:

npm publish --tag canary

# then later...
npm tag some@1.2.5 stable
Member

isaacs commented Aug 15, 2012

Also, you can do it in one step, if you like:

npm publish --tag canary

# then later...
npm tag some@1.2.5 stable

@xdissent xdissent referenced this issue in karma-runner/karma Jun 11, 2013

Closed

Update package with npm #563

@pvdlg pvdlg referenced this issue in semantic-release/semantic-release Nov 27, 2017

Closed

docs: Update readme for 0.x.x #532

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.