ci(root): skip broken yarn audit step in release workflows#9262
Merged
Conversation
roshan-bitgo
force-pushed
the
fix/audit-continue-on-error
branch
from
3286efa to
92f408a
Compare
Contributor
roshan-bitgo
changed the title
diksha190
approved these changes
Jul 15, 2026
diksha190
left a comment
diksha190
left a comment
There was a problem hiding this comment.
LGTM , Approving with the understanding that this is a pragmatic hotfix.
Rationale:
- The yarn audit step is already non-functional due to npm retiring the legacy security endpoint (HTTP 410), so continue-on-error: true doesn't regress our security posture, it just acknowledges reality
- This unblocks critical releases that are currently stuck
- The change is minimal, low-risk, and well-documented
- Follow-up migration to osv-scanner is committed in the PR description
hrishikeshjain
approved these changes
Jul 15, 2026
Marzooqa
approved these changes
Jul 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
4 participants
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.
Summary
yarn auditpermanently broken as of 2026-07-15 — npm retired the legacy security audits endpoint (/-/npm/v1/security/audits) with HTTP 410. Bothpublish.ymlandnpmjs-release.ymlfail at theAudit Dependenciesstep. The yarn team closed the fix as "not planned" — this is permanent.This adds
continue-on-error: trueto both audit steps to unblock releases. The security gate is currently non-functional regardless, so this does not regress our security posture.A proper fix migrating to
osv-scanner(readsyarn.lockdirectly, no npm registry dependency) is tracked in VL-7134.Files changed
.github/workflows/publish.yml.github/workflows/npmjs-release.ymlFixes: VL-7134