Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Title should be changed to 5.7.0 as newly released 5.7.1 fixes the bug.


Maturely tagged with `#STOPUSINGPRERELEASESWITHSUDO`

When their Official Blog makes no mention of 5.7.0 being a prelease [0] and is semantically versioned as a stable release. The thread also later details that running `npm upgrade -g npm` instead of `npm install -g npm`will get 5.7.0 instead of 5.6.0 [1].

Is it standard practice for an `upgrade` command to pull a pre-release or beta? When I upgrade Firefox I don't get put onto the Nightly branch...

[0] https://vgy.me/LkvBKS.png

[1] https://github.com/npm/npm/issues/19883#issuecomment-3677268...


This is relevant to the information I posted in my comment here how?

It is not.





Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: