Repository navigation
Run npm audit with npm 11 in CI - #14
Merged
Merged
Conversation
The npm bundled with Node 22 calls an audit endpoint that the registry is retiring and now answers HTTP 400, which fails every CI run regardless of the change. npm 11 uses the bulk advisory endpoint. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Gary Schaetz <gary@schaetzkc.com>
This file contains hidden or 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
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.
What changed
The
npm auditstep in.github/workflows/ci.ymlnow runsnpx --yes npm@11 audit --audit-level=moderate.Why
CI has started failing on every PR at
npm auditwith400 Bad Request … This endpoint is being retired. Use the bulk advisory endpoint instead. The npm bundled with Node 22 still calls the oldaudits/quickendpoint, which the registry no longer accepts. npm 11 uses the bulk advisory endpoint: locallynpm audit --audit-level=moderate(npm 11.20) reports 0 vulnerabilities on this lockfile. This blocked the docs fix in #13 although its change cannot affect it.Testing
pnpm test: 343 passed. The audit step itself can only be proven by this PR's own CI run. No source or dependency change.Docs updated
None needed (CI configuration only).
🤖 Generated with Claude Code