deps: upgrade npm to 6.11.2

[isaacs]

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

• 9778a1b87cmd-shim@3.0.3: Fix regression where shims fail to preserve exit code (@isaacs)
• bf93e91d8npm-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

• 291aba7b8 make tests pass on Windows (@isaacs)
• fea3a023a travis: run tests on Windows as well (@isaacs)

[trivikr]

RSLGTM

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/25191/

[Trott]

Rubber-stamp LGTM

[Trott]

This can land on or after September 5.

[Trott]

CITGM: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/1977/

[ZYSzys]

RSLGTM

[danbev]

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]

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]

Superseded by #29430.