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

npm -g i npm@v1.4 installs from v1.4-next #6082

Closed
mgol opened this Issue Sep 1, 2014 · 4 comments

Comments

Projects
None yet
4 participants
@mgol

mgol commented Sep 1, 2014

$ npm --version
1.4.26
$ npm info npm dist-tags

{ latest: '2.0.0-beta.0',
  'v2.0rc': '2.0.0-beta.0',
  next: '2.0.0-beta.2',
  'v1.4-next': '1.4.26',
  'v2.0-next': '2.0.0-beta.2',
  'v1.4': '1.4.25' }

$ npm -g i npm@v1.4
/Users/mgol/.nvm/v0.11.13/bin/npm -> /Users/mgol/.nvm/v0.11.13/lib/node_modules/npm/bin/npm-cli.js
npm@1.4.26 /Users/mgol/.nvm/v0.11.13/lib/node_modules/npm
$ npm --version
1.4.26

I'm on OS X 10.9.4, Node.js installed via nvm.

@othiym23 othiym23 modified the milestone: 2.0.0 Sep 2, 2014

@othiym23 othiym23 added the bug label Sep 2, 2014

@othiym23

This comment has been minimized.

Show comment
Hide comment
@othiym23

othiym23 Sep 2, 2014

Contributor

Confirmed, but this is really a bug in how we're using tags: node-semver treats v1.4 as 1.4 as 1.4.x, so it's installing the newest version of 1.4 and not the dist-tag. We'll come up with a new way to tag these things, and leaving this issue open to track that.

Contributor

othiym23 commented Sep 2, 2014

Confirmed, but this is really a bug in how we're using tags: node-semver treats v1.4 as 1.4 as 1.4.x, so it's installing the newest version of 1.4 and not the dist-tag. We'll come up with a new way to tag these things, and leaving this issue open to track that.

@isaacs

This comment has been minimized.

Show comment
Hide comment
@isaacs

isaacs Sep 2, 2014

Member

Best suggestion is probably to have the client refuse to tag things with a tag name that is a valid semver range. After a year or two of that in the client, we can enforce on the server.

Member

isaacs commented Sep 2, 2014

Best suggestion is probably to have the client refuse to tag things with a tag name that is a valid semver range. After a year or two of that in the client, we can enforce on the server.

@mgol

This comment has been minimized.

Show comment
Hide comment
@mgol

mgol Sep 3, 2014

We publish the jQuery 1.x branch under the 1.x tag, IIRC that was your recommendation, @isaacs. It was supposed to look at tags first and only afterwards at semver ranges, wasn't it? cc @scottgonzalez @dmethvin

What will happen to existing semver-range-like tags? Will we be able to unpublish them with the new npm?

mgol commented Sep 3, 2014

We publish the jQuery 1.x branch under the 1.x tag, IIRC that was your recommendation, @isaacs. It was supposed to look at tags first and only afterwards at semver ranges, wasn't it? cc @scottgonzalez @dmethvin

What will happen to existing semver-range-like tags? Will we be able to unpublish them with the new npm?

@smikes

This comment has been minimized.

Show comment
Hide comment
@smikes

smikes Feb 23, 2015

Contributor

What will happen to existing semver-range-like tags? Will we be able to unpublish them with the new npm?

Yes, this is now supported as of npm@2.5.0 -- you can remove dist-tags with

npm dist-tag rm jquery 1.x
Contributor

smikes commented Feb 23, 2015

What will happen to existing semver-range-like tags? Will we be able to unpublish them with the new npm?

Yes, this is now supported as of npm@2.5.0 -- you can remove dist-tags with

npm dist-tag rm jquery 1.x
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.