Skip to content
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

Closed
wants to merge 1 commit into from
Closed

deps: upgrade npm to 6.11.2 #29273

wants to merge 1 commit into from

Conversation

isaacs
Copy link
Contributor

@isaacs isaacs commented Aug 22, 2019

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 cmd-shim@3.0.3: Fix regression where shims fail to preserve exit code (@isaacs)
  • bf93e91d8 npm-package-arg@6.1.1: 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

@nodejs-github-bot nodejs-github-bot added the npm Issues and PRs related to the npm client dependency or the npm registry. label Aug 22, 2019
Copy link
Member

@trivikr trivikr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RSLGTM

@nodejs-github-bot
Copy link
Collaborator

Copy link
Member

@Trott Trott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rubber-stamp LGTM

@Trott
Copy link
Member

Trott commented Aug 23, 2019

This can land on or after September 5.

@Trott
Copy link
Member

Trott commented Aug 23, 2019

Copy link
Member

@ZYSzys ZYSzys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RSLGTM

@danbev
Copy link
Contributor

danbev commented Aug 26, 2019

This can land on or after September 5.

@Trott Just curious about the reason for waiting until September 5 for this? (just for future reference)

@Trott
Copy link
Member

Trott commented Aug 26, 2019

This can land on or after September 5.

@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.

@lpinca
Copy link
Member

lpinca commented Oct 12, 2019

Superseded by #29430.

@lpinca lpinca closed this Oct 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
npm Issues and PRs related to the npm client dependency or the npm registry.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants