deps: upgrade npm in LTS to 2.15.2 #6150
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
zkat
added
npm
|
I'm going to start testing this once we get 4.4.3 out tomorrow 😄 |
|
Landed in 9200d18...c92febf |
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.
Checklist
Affected core subsystem(s)
depstoolsDescription of change
Hey all! I come bearing npm LTS goodness! 👯
This is a fairly minor release with just some test-suite-related cleanup and documentation updates. Nothing of significance beyond that.
I also included a patch in this PR to get rid of the call to
test-legacyintools/test-npm.sh, since legacy tests are no longer run separately.The changelog is over here: https://github.com/npm/npm/releases/tag/v2.15.2
r: @iarna
r: @thealphanerd
r: @Fishrock123