-
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 npm to 2.14.9 (for v0.12-staging) #3684
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
othiym23
added
npm
Issues and PRs related to the npm client dependency or the npm registry.
land-on-v0.12
labels
Nov 6, 2015
This is a roll-up release that includes all changes to npm since 2.13.4.
othiym23
force-pushed
the
npm-2.14.9-node-0.12
branch
from
November 6, 2015 02:57
7f65c8d
to
31571a3
Compare
Whitespace fix applied, and force-pushed. Also, reminded myself to read the release process docs more carefully in the future. 🎉 |
Hmm, patch doesn't like applying for me, same base.
|
Test pass fine. Looks like the diff is too big for me to go though, so rubber-stamp-ish LGTM. |
LGTM |
othiym23
added a commit
that referenced
this pull request
Nov 15, 2015
This is a roll-up release that includes all changes to npm since 2.13.4. PR-URL: #3684 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Landed in |
jBarz
pushed a commit
to ibmruntimes/node
that referenced
this pull request
Nov 4, 2016
This is a roll-up release that includes all changes to npm since 2.13.4. PR-URL: nodejs/node#3684 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(I'll create a separate PR for v4.x-staging.)
This is a rollup release that includes everything since
npm@2.13.4
, so much has changed. SeeCHANGELOG.md
for details. I ranmake test-npm
against this and everything passed, but it would be good to get confirmation from someone in the release WG.r: @Fishrock123