-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
deps: upgrade to npm 2.14.11 #4003
Conversation
This is causing serious issues :(
Any suggestions on how we should approach |
I'd like to say it'll be easy enough to cherry-pick -- I'll give it a shot myself in the morning and see if there's any issues . I also seem to have run into some test failures, so we should hold off on this PR for now, anyway. With all the messing around I was doing, I forgot to run the test suite before submitting this PR -- argh! :/ |
seemed to work well enough to me (this is assuming we want to ignore all conflicts and just accept all npm changes in this commit edit: this was against 0.12.8-rc fwiw |
Thanks, Myles! ^_^ |
Fwiw I'm getting these errors:
|
Yep! That's why I was asking you about prereleases. You'll need to edit That's because semver considers prereleases to not exist in ranges, so all the engine checks, including |
See #4033 -- I think this PR is safe to close. |
Heya!
Here's a new LTS release. Check out the changelog: https://github.com/npm/npm/releases/tag/v2.14.11
The main thing to note is a hopefully welcome update to our licensing to clarify scope of both the open source side and the registry TOS.
For some reason, I ran into the infamous
Readme.md
/README.md
git-on-OSX issue again. I tried reproducing my previous steps and they didn't seem to work -- The extra commit you see is what I think the correct final fix for this. It seems that theReadme.md
somehow still stuck around after we removed it from the npm repo proper. It should be completely gone now. 🙏r: @jasnell
r: @Fishrock123
r: @chrisdickinson