fix(ci): ignore pnpm audit registry errors while npm retires legacy endpoints#2004
Merged
fix(ci): ignore pnpm audit registry errors while npm retires legacy endpoints#2004
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the reusable Security Checks workflow to keep CI pipelines unblocked while pnpm audit is failing due to npm retiring legacy audit endpoints, relying on the existing Grype scan for vulnerability coverage in the interim.
Changes:
- Add
--ignore-registry-errorsto thepnpm auditCI step to tolerate registry-side audit endpoint failures.
JAORMX
approved these changes
Apr 15, 2026
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.
The npm registry has retired both legacy audit endpoints (
/-/npm/v1/security/audits/quickand/-/npm/v1/security/audits), returning HTTP 410. This breakspnpm auditon all 10.x versions (tracked in pnpm/pnpm#11265). There is no released pnpm version yet that supports the replacement bulk advisory endpoint.Add
--ignore-registry-errorsto the CI audit step so pipelines are not blocked while a proper fix lands in pnpm. Grype still provides vulnerability scanning coverage in the same workflow.