deps: upgrade npm to 6.4.0 #22342
Closed
deps: upgrade npm to 6.4.0 #22342
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
nodejs-github-bot
added
the
npm
2 tasks
|
Yes, I'm aware of the policy, seeing as I was part of the discussion for it. :) |
|
This PR needs a rebase against master to avoid the git failure in the CI. |
|
@joyeecheung would it not be sufficient to rebase on the CI task? |
|
I've rebased it 👍 |
|
Moving this to #22591, since 6.4.1 came out in the meantime 😅 |
|
Doesn't that mean we have to wait another 2 weeks to get npm@6.4.x integrated? |
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
make -j4 test(UNIX), orvcbuild test(Windows) passesWhere this should land
Notable Changes
This release includes two versions of npm, including the current
latestrelease,npm@6.4.0.f861c2b57node-gyp@3.8.0: This means our entire npm dep tree now uses the latestnode-gyp, and we've updated and flattenedrequestas well.npm auditon npm itself comes up clean now! (@rvagg)6e9f04b0bnpm/cli#8 Search for authentication token defined by environment variables by preventing the translation layer from env variable to npm option from breaking:_authToken. (@mkhl)84bfd23e7npm/cli#35 Stop filtering out non-IPv4 addresses fromlocal-addrs, making npm actually use IPv6 addresses when it must. (@valentin2105)d81146181npm/cli#32 Don't check for updates to npm when we are updating npm itself. (@olore)Another reminder that we've moved our issue tracking! You can read more about our move away from GitHub for issue tracking on our blog
Changelogs