Skip to content

Conversation

@othiym23
Copy link
Contributor

https://github.com/npm/npm/releases/tag/v2.11.0 has the details – new hooks for preversion, version, and postversion lifecycle events, and a bunch of SPDX-related license changes and license file inclusions.

r: @Fishrock123
r: @chrisdickinson

othiym23and others added 3 commits May 28, 2015 22:29
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 <[email protected]>
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 <[email protected]>
@othiym23othiym23 added the npm Issues and PRs related to the npm client dependency or the npm registry. label May 29, 2015
@Fishrock123
Copy link
Contributor

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 win,node-gyp: enable delay-load hook thing, specifically in that it can't be backported. However, I don't think backporting these is really ideal anyways. When we want to do a 1.8.3 I'll probably just do one of these myself for it, unless npm wants to.

othiym23 added a commit that referenced this pull request May 30, 2015
PR-URL: #1829 Reviewed-By: Jeremiah Senkpiel <[email protected]>
@othiym23
Copy link
ContributorAuthor

will land into 2.2.0 (#1808) if it doesn't beforehand.

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 [email protected] (not sure how far along in the release process he was / is).

When we want to do a 1.8.3 I'll probably just do one of these myself for it, unless npm wants 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!

@othiym23othiym23 deleted the npm-2.11.0 branch May 30, 2015 12:22
@Fishrock123
Copy link
Contributor

@othiym23 yep, landing is master is correct, 2.2.0 will be released from it soon. :)

@rvaggrvagg mentioned this pull request May 31, 2015
@targostargos mentioned this pull request May 31, 2015
andrewdeandrade pushed a commit to andrewdeandrade/node that referenced this pull request Jun 3, 2015
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

npmIssues and PRs related to the npm client dependency or the npm registry.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@othiym23@Fishrock123@cjihrig@piscisaureus