-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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 6.11.2 #29273
deps: upgrade npm to 6.11.2 #29273
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RSLGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rubber-stamp LGTM
This can land on or after September 5. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RSLGTM
@Trott Just curious about the reason for waiting until September 5 for this? (just for future reference) |
We have a rule that new npm versions wait two weeks after their release before landing them in Node.js master. That caution may be outdated and we may wish to revisit it. Or maybe it is serving us well. But in either case, I post those notes because people (understandably) forget that npm PRs are handled differently from other PRs. |
Superseded by #29430. |
This fixes the last of the Windows regressions in 6.11.0.
Changelog:
6.11.2 (2019-08-22):
Fix a recent Windows regression, and two long-standing Windows bugs. Also, get CI running on Windows, so these things are less likely in the future.
DEPENDENCIES
9778a1b87
[email protected]
: Fix regression where shims fail to preserve exit code (@isaacs)bf93e91d8
[email protected]
: Properly handle git+file: urls on Windows when a drive letter is included. (@isaacs)BUGFIXES
6cc4cc66f
escape args properly on Windows Bash Despite being bash, Node.js running on windows git mingw bash still executes child processes using cmd.exe. As a result, arguments in this environment need to be escaped in the style of cmd.exe, not bash. (@isaacs)TESTS
291aba7b8
make tests pass on Windows (@isaacs)fea3a023a
travis: run tests on Windows as well (@isaacs)