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

"npm tag" is unsupported #8

Closed
rlidwka opened this issue Oct 2, 2013 · 1 comment
Closed

"npm tag" is unsupported #8

rlidwka opened this issue Oct 2, 2013 · 1 comment

Comments

@rlidwka
Copy link
Owner

rlidwka commented Oct 2, 2013

...

@rlidwka
Copy link
Owner Author

rlidwka commented Dec 7, 2013

Proposal:

  1. dist-tags is a hash "tag -> array of versions", not "tag -> version"
  2. when we are retrieving something, return highest version having this tag
  3. once you tag something, there is no way to remove that tag except for unpublishing
  4. latest tag always returns highest available version, because current magic is just stupid

This would allow something like that:

npm tag something@1.2.3 production
# "dist-tags":{"production":['1.2.3']}
npm install something@production # installs 1.2.3
npm tag something@1.2.4 production
# "dist-tags":{"production":['1.2.3','1.2.4']}
npm install something@production # installs 1.2.4
npm unpublish something@1.2.4
# "dist-tags":{"production":['1.2.3']}
npm install something@production # installs 1.2.3

rlidwka added a commit that referenced this issue Dec 8, 2013
aeweidne added a commit to aeweidne/sinopia that referenced this issue Jun 28, 2016
rmg added a commit to strongloop-forks/sinopia that referenced this issue Oct 28, 2016
If packages are being published to verdaccio as well as upstream to
npmjs.org, then when the cache is updated from npmjs.org it uses the
dist-tags from the upstream even if the locally published version is
actually newer. This makes it very difficult to use verdaccio as a
staging registry for testing out potential releases.

This change partially reverts a change in behaviour that was introduced
in rlidwka#8 which caused a regression for the staging style workflow that was
supported by sinopia.
rmg added a commit to strongloop-forks/sinopia that referenced this issue Oct 28, 2016
If packages are being published to verdaccio as well as upstream to
npmjs.org, then when the cache is updated from npmjs.org it uses the
dist-tags from the upstream even if the locally published version is
actually newer. This makes it very difficult to use verdaccio as a
staging registry for testing out potential releases.

This change partially reverts a change in behaviour that was introduced
in rlidwka#8 which caused a regression for the staging style workflow that was
supported by sinopia.
rmg added a commit to strongloop-forks/sinopia that referenced this issue Dec 21, 2016
If packages are being published to verdaccio as well as upstream to
npmjs.org, then when the cache is updated from npmjs.org it uses the
dist-tags from the upstream even if the locally published version is
actually newer. This makes it very difficult to use verdaccio as a
staging registry for testing out potential releases.

This change partially reverts a change in behaviour that was introduced
in rlidwka#8 which caused a regression for the staging style workflow that was
supported by sinopia.
rmg added a commit to strongloop-forks/sinopia that referenced this issue Jun 1, 2017
If packages are being published to verdaccio as well as upstream to
npmjs.org, then when the cache is updated from npmjs.org it uses the
dist-tags from the upstream even if the locally published version is
actually newer. This makes it very difficult to use verdaccio as a
staging registry for testing out potential releases.

This change partially reverts a change in behaviour that was introduced
in rlidwka#8 which caused a regression for the staging style workflow that was
supported by sinopia.
rmg added a commit to strongloop-forks/sinopia that referenced this issue Jun 1, 2017
If packages are being published to verdaccio as well as upstream to
npmjs.org, then when the cache is updated from npmjs.org it uses the
dist-tags from the upstream even if the locally published version is
actually newer. This makes it very difficult to use verdaccio as a
staging registry for testing out potential releases.

This change partially reverts a change in behaviour that was introduced
in rlidwka#8 which caused a regression for the staging style workflow that was
supported by sinopia.
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