ci(root): fix osv-scanner severity flag and continue on error#9311
Merged
Conversation
osv-scanner v2.3.8 does not support the --severity flag, causing Audit Dependencies to fail with exit 127 (flag provided but not defined: -severity). Remove --severity=HIGH/CRITICAL from scan-args in publish.yml and npmjs-release.yml. Also add continue-on-error so future audit failures never block a release while the osv-scanner setup is iterated on. TICKET: VL-7134
yashvanthbl137-crypto
approved these changes
Jul 21, 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
2 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.
Problem
The "Audit Dependencies" step in
publish.ymlandnpmjs-release.ymlfails with exit 127 because osv-scanner v2.3.8 no longer supports the--severity=HIGH/--severity=CRITICALflag that was being passed as scan-args.Failing run: https://github.com/BitGo/BitGoJS/actions/runs/29828802882/job/88628278879
Fix
--severityscan-args from the Audit Dependencies step in both workflows.continue-on-error: trueto that step (explicit request) so releases are never blocked by audit failures while the audit setup is iterated on.Related prior fix attempt: #9310
TICKET: VL-7134