-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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.11.0 #1829
Conversation
Every npm version bump requires a few patches to be floated on node-gyp for io.js compatibility. These patches are found in 03d1992, 5de334c, and da730c7. This commit squashes them into a single commit. PR-URL: nodejs#990 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
The delay-load hook allows node.exe/iojs.exe to be renamed. See efadffe for more background. This commit is a combined squash of the following previous patches: ba93c58, 3bda6cb, 0d6d3dd. PR-URL: nodejs#1763 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
LGTM, will land into 2.2.0 (#1808) if it doesn't beforehand. I may have made a bit of an oops squashing the entire |
PR-URL: #1829 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
It's on master now (as c1afa53, f9fd554, and 53e98cc) – I've left a note for @rvagg leaving up to him whether he wants to pull it from master to
I will not say no to someone volunteering to help out. You probably already have seen this, but here is the workflow that npm follows for preparing io.js for a new npm release, and it's probably just as easy for you to do it as us. Thanks! |
@othiym23 yep, landing is master is correct, 2.2.0 will be released from it soon. :) |
PR-URL: nodejs/node#1829 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
https://github.com/npm/npm/releases/tag/v2.11.0 has the details – new hooks for
preversion
,version
, andpostversion
lifecycle events, and a bunch of SPDX-related license changes and license file inclusions.r: @Fishrock123
r: @chrisdickinson