Nuxt.js: (docs) yarn/npm upgrade installs rc9 instead of rc11

Created on 14 Oct 2017  Â·  11Comments  Â·  Source: nuxt/nuxt.js

As I could not find information about this anywhere, it would be nice if the docs could list the following issue. Due to a bug/feature in SemVer check, version rc9 is regarded as a higher version then eg rc11. See https://jubianchi.github.io/semver-check/, put ^1.0.0-rc9 on the left and 1.0.0-rc11 on the right.

This means that if you run eg yarn upgrade it will by default install rc9. The funny thing is, if you run yarn upgrade nuxt@latest it does install rc11.

Both npm outdated as yarn outdated reflect this issue:

$ npm outdated
Package      Current       Wanted         Latest  Location
nuxt      1.0.0-rc11    1.0.0-rc9     1.0.0-rc11  

$ yarn outdated
yarn outdated v1.1.0
Package Current    Wanted    Latest     Package Type URL                                   
nuxt    1.0.0-rc11 1.0.0-rc9 1.0.0-rc11 dependencies https://github.com/nuxt/nuxt.js#readme
Done in 0.99s.

Relevant yarn issue: https://github.com/yarnpkg/yarn/issues/3560

I guess this was the same reason why in the past you switched from alpha2 to alpha.2?

This question is available on Nuxt.js community (#c1669)
available soon

Most helpful comment

Yes but I would like to show that these last rc are the last one:

  • Release Candidate A -> rca
  • Release Candidate B -> rcb

So we can tell everyone to upgrade to rca without having to give a number (even if it's not perfect Semverâ„¢). I don't think they will last for long anyway :)

All 11 comments

1.0.0-rc11 < 1.0.0-rc9
1.0.0-rc.11 1.0.0-rc.9
Not having a dot makes them compare alphabetically.
This happens very often.
npm doesn't have epoch, so fixing this is awkward.

Next version has to be something like 1.0.0-rca.12 to get all of the -rc9 users to update.

Funnily enough, 1.0.1-rc.12 wouldn't satisfy ^1.0.0-rc11 either.

Next release will be 1.0.1-rc.12, thank you @pimlie @qm3ster for this precious information :)

That won't work :open_mouth:

@qm3ster what do you suggest instead? 1.0.0-rca.12?

As ugly it is, yeah. That correctly updates everyone and will be fixed once 1.0.0 is out.

Actually I would like to have 1 or 2 RC left before official 1.0 :/

What about 1.0.0-rca, then 1.0.0-rcb and finally 1.0.0

Ping @alexchopin @pi0

There's also -rc9[1-9] range :stuck_out_tongue:
But although I doubt there will be 8 more versions before 1.0, my vote is for a variant that compares the last group numerically, eg -rca.12 (-rca.1 would confuse people) because that's Semverâ„¢ and stands for Reeleeze CAndidate

Yes but I would like to show that these last rc are the last one:

  • Release Candidate A -> rca
  • Release Candidate B -> rcb

So we can tell everyone to upgrade to rca without having to give a number (even if it's not perfect Semverâ„¢). I don't think they will last for long anyway :)

There hasn't been a release in a while, but lots of commits every day. Is there some blocking issue preventing a release?

Congratulations :confetti_ball:

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

vadimsg picture vadimsg  Â·  3Comments

bimohxh picture bimohxh  Â·  3Comments

danieloprado picture danieloprado  Â·  3Comments

vadimsg picture vadimsg  Â·  3Comments

bimohxh picture bimohxh  Â·  3Comments