Bump the npm-dependencies group across 1 directory with 3 updates#13280
Conversation
14f03d5 to
f941a9b
Compare
2016bff to
a66417c
Compare
dc5f332 to
33feb43
Compare
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
33feb43 to
af5cea6
Compare
58f5c1e to
763ad1c
Compare
175c798 to
d301dd8
Compare
d301dd8 to
6b8efdd
Compare
8a41438 to
23abca0
Compare
74d57d5 to
d4bdc20
Compare
d90f220 to
f0449ef
Compare
|
@dependabot recreate |
f0449ef to
cf73dd2
Compare
|
@dependabot rebase |
cf73dd2 to
d847f3e
Compare
|
I dug into the CI failure. Both The problem is nock v14 and arborist v9 don't play well together. nock v13 intercepted HTTP by monkey-patching The semver bump is fine. The arborist and nock bumps are individually fine too, but combined they break the vulnerability auditor's mocking setup. Easiest fix: split this into two PRs. Take arborist v9 + semver now, keep nock at v13. The nock v14 upgrade needs either a workaround in |
|
Pushed a fix in f26a558. Replaced nock with a real |
f26a558 to
7e23757
Compare
|
Pushed a second fix in c89ca6a. The smoke test Fix: pass |
Bumps the npm-dependencies group with 3 updates in the /npm_and_yarn/helpers directory: [@npmcli/arborist](https://github.com/npm/cli/tree/HEAD/workspaces/arborist), [nock](https://github.com/nock/nock) and [semver](https://github.com/npm/node-semver). Updates `@npmcli/arborist` from 8.0.0 to 9.1.6 - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/workspaces/arborist/CHANGELOG.md) - [Commits](https://github.com/npm/cli/commits/arborist-v9.1.6/workspaces/arborist) Updates `nock` from 13.5.6 to 14.0.10 - [Release notes](https://github.com/nock/nock/releases) - [Changelog](https://github.com/nock/nock/blob/main/CHANGELOG.md) - [Commits](nock/nock@v13.5.6...v14.0.10) Updates `semver` from 7.7.2 to 7.7.3 - [Release notes](https://github.com/npm/node-semver/releases) - [Changelog](https://github.com/npm/node-semver/blob/main/CHANGELOG.md) - [Commits](npm/node-semver@v7.7.2...v7.7.3) --- updated-dependencies: - dependency-name: "@npmcli/arborist" dependency-version: 9.1.6 dependency-type: direct:production update-type: version-update:semver-major dependency-group: npm-dependencies - dependency-name: nock dependency-version: 14.0.10 dependency-type: direct:production update-type: version-update:semver-major dependency-group: npm-dependencies - dependency-name: semver dependency-version: 7.7.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: npm-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
nock v14 uses @mswjs/interceptors, which intercepts at the socket level. arborist v9 uses @npmcli/agent (via npm-registry-fetch v19), which wraps connections through agent-base. The two don't talk to each other: nock calls Agent.createConnection() expecting a raw net.Socket, agent-base returns nothing it understands, and the audit request hangs. Swap nock out for a plain http.createServer on a random port. The server responds to POST /-/npm/v1/security/advisories/bulk with the same JSON nock was returning. This works with any HTTP client/agent and removes nock as a production dependency entirely.
In CI, HTTP traffic goes through a proxy container. The local http.createServer used for faking the audit registry listens on 127.0.0.1, but arborist (via npm-registry-fetch) routes requests through the proxy, which can't reach localhost. The proxy logs showed 'No response from server' for the bulk advisory POST. Pass noProxy: '127.0.0.1' in the Arborist options so the audit request goes directly to the local server.
c89ca6a to
bc6d524
Compare
Bumps the npm-dependencies group with 3 updates in the /npm_and_yarn/helpers directory: @npmcli/arborist, nock and semver.
Updates
@npmcli/arboristfrom 8.0.0 to 9.1.6Release notes
Sourced from
@npmcli/arborist's releases.... (truncated)
Changelog
Sourced from
@npmcli/arborist's changelog.... (truncated)
Commits
0722535chore: release 11.6.20a8b8c2fix: typo bugs and other spelling fixes (#8621)54fd27ffix: refactor node.ideallyInert to node.inert (#8602)13d8df6fix: optional set calculation (#8537)180e9f7chore: fix spelling in workspaces/arborist (#8610)91393dechore: Update references for arborist to cli (#8599)c4ba7f4chore: release 11.6.160aa94bfix: attach path to json parse error4059dfachore: properly use arborist and cache in test402a0abchore:@npmcli/template-oss@4.25.1Maintainer changes
This version was pushed to npm by owlstronaut, a new releaser for
@npmcli/arboristsince your current version.Updates
nockfrom 13.5.6 to 14.0.10Release notes
Sourced from nock's releases.
... (truncated)
Commits
f2a3389fix: Use Error objects instead of plain objects with replyWithError() (#2900)721ae1achore(deps-dev): bump form-data from 4.0.2 to 4.0.4316c990chore(deps-dev): bump tmp from 0.2.1 to 0.2.4bc48f92fix: address timeout issue with mocked timers (Revert #2880) (#2902)e4390b8fix(ClientRequest): support http.Agent instances as agents for https requests...fb112f3fix: address timeout issue with mocked timers (#2880)0db794bfixeeb0924fixb77f865testb4514cafixUpdates
semverfrom 7.7.2 to 7.7.3Release notes
Sourced from semver's releases.
Changelog
Sourced from semver's changelog.
Commits
a25789bchore: release 7.7.3 (#812)e37e0cafix: faster paths for compare (#813)2471d75fix: x-range build metadata support8f05c87chore: bump@npmcli/template-ossfrom 4.25.0 to 4.25.1 (#807)d17aebfchore: bump@npmcli/template-ossfrom 4.24.4 to 4.25.0 (#797)3b03e3bchore: bump@npmcli/template-ossfrom 4.24.3 to 4.24.4 (#790)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for semver since your current version.
You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions