This repository was archived by the owner on Apr 22, 2023. It is now read-only.
deps: upgrade npm to 2.6.1 #9297
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
|
LGTM and @joyent/node-coreteam Any objection? |
|
LGTM |
1 similar comment
|
LGTM |
misterdjules
pushed a commit
to misterdjules/node
that referenced
this pull request
Mar 3, 2015
PR: nodejs#9297 PR-URL: nodejs#9297 Reviewed-By: Julien Gilli <julien.gilli@joyent.com> Reviewed-By: Trevor Norris <trev.norris@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
|
Thank you! Landed in 63fbd10. |
|
Thank you, @misterdjules / everybody! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is a comparatively modest update, at least compared to
npm@2.7.0, which includes at least one feature that is very relevant to io.js's interests (foreshadowing!). Here are the pertinent changes innpm@2.6.1:8b98f0e#4471
npm outdated(and onlynpm outdated) now defaults to--depth=0. This also has the excellent but unexpected effect of makingnpm update -gwork the way almost everyone wants it to. See the docs for--depthfor the mildly confusing details. (@smikes)
aa79194#6565 Tweak
peerDependencydeprecation warning to include which peer dependency on which package is
going to need to change. (@othiym23)
5fa067f#7171 Tweak
engineStrictdeprecation warning to include which
package.jsonis using it.(@othiym23)
This PR also includes all of the changes in
npm@2.6.0:38c4825#5068 Add new logout command, and make it do something useful on both bearer-based and basic-based authed clients. (@othiym23)c8e08e6#6565 Warn thatpeerDependencybehavior is changing and add a note to the docs. (@othiym23)7c81a5f#7171 Warn thatengineStrictinpackage.jsonwill be going away in the next major version of npm (coming soon!) (@othiym23)