fix(root): unblock beta releases blocked by medium vulnerabilities#9330
Closed
bitgo-ai-agent-dev[bot] wants to merge 1 commit into
Closed
fix(root): unblock beta releases blocked by medium vulnerabilities#9330bitgo-ai-agent-dev[bot] wants to merge 1 commit into
bitgo-ai-agent-dev[bot] wants to merge 1 commit into
Conversation
Address OSV scanner failures in the publish workflow that began blocking beta releases after `continue-on-error` was removed on 2026-07-21 (commit 42b31a5). The scanner found 36 vulnerabilities — 30 Medium and 6 Low — with no Critical or High remaining after prior fixes. **What changed:** package.json resolutions and overrides: - body-parser 1.20.3 → 1.20.6 (GHSA-v422-hmwv-36x6) - protobufjs 7.6.4 → 7.6.5 (GHSA-j3f2-48v5-ccww) - dompurify 3.4.11 → 3.4.12 (GHSA-c2j3-45gr-mqc4) - webpack-dev-server 5.2.1 → 5.2.6 (GHSA-79cf/f5vj/m28w/mx8g) - ws 8.18.3 → 8.20.1; add global ws 8.20.1 (GHSA-58qx-3vcg-4xpx) - ajv pinned to 8.18.0 (GHSA-2g4f-4pwh-qvx6) - bn.js pinned to 5.2.3 (GHSA-378v-28hj-76wf) - diff pinned to 5.2.2 (GHSA-73rr-hh4g-fpgx) - http-proxy-middleware pinned to 2.0.10 (GHSA-64mm-vxmg-q3vj) - yaml pinned to 2.8.3 (GHSA-48c2-rrv3-qjmp) osv-scanner.toml: - Remove stale GHSA-wcpc-wj8m-hjx6 (protobufjs bumped to 7.6.5) - Add ignores for: @octokit/* old versions (dev tooling, major upgrade needed), @stablelib/ed25519 (no fix), aws-sdk 2.x (no fix), elliptic 6.x (no fix), ip-address 9.x (major version), tar 6.x/7.x new CVEs (same lerna constraint), ws residual instances (client-only usage) **Why:** Beta releases are blocked because the OSV scanner finds medium vulnerabilities and fails the CI step. Several have easy patch-version fixes; the rest are accepted risks (dev-only tooling, no patched version, or require a major breaking upgrade). This unblocks the OVC release as well as ongoing beta publish workflows. Ticket: CTX-271 Session-Id: cdc043f4-5f33-4cd0-97bf-07f5617341e6 Task-Id: 1d743ffa-02cc-4a83-aaf5-1b290de75f98
Contributor
bitgo-ai-agent-dev
Bot
force-pushed
the
fix/CTX-271-unblock-beta-release-vulnerability-scan
branch
from
July 22, 2026 18:36
2d2c187 to
342e268
Compare
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
body-parser1.20.3 → 1.20.6,protobufjs7.6.4 → 7.6.5,dompurify3.4.11 → 3.4.12,webpack-dev-server5.2.1 → 5.2.6 inresolutions/overrideswsto 8.20.1 (also updateavalanche-scoped override); addajv8.18.0,bn.js5.2.3,diff5.2.2,http-proxy-middleware2.0.10,yaml2.8.3GHSA-wcpc-wj8m-hjx6ignore fromosv-scanner.toml(now fixed via protobufjs bump)@octokit/*v2/v5 (dev-time tooling, major upgrade needed),@stablelib/ed25519(no fix),aws-sdkv2 (no fix, v3 migration is separate),elliptic6.x (no fix),ip-address9.x (major breaking upgrade),tar6.x/7.x new CVEs (same lerna packDirectory constraint),wsresidual instances (client-only usage)Why
continue-on-errorwas removed from theAudit Dependenciesstep in.github/workflows/publish.yml(commit 42b31a5). The OSV scanner now exits with code 1 whenever it finds any unignored vulnerability, and 36 vulnerabilities (30 Medium, 6 Low) that were previously present but tolerated are now blocking every publish run. This is preventing OVC and other team releases.resolutions/overrides. Where fixes require a major breaking upgrade or no upstream fix exists, the vulnerabilities are documented with rationale and added to the ignore list, consistent with the existing pattern inosv-scanner.toml.Test plan
Publish @bitgo-betaworkflow manually — theAudit Dependenciesstep should pass (exit 0)osv-scanner.tomlreports no unused ignores after the protobufjs bump removesGHSA-wcpc-wj8m-hjx6@bitgo-betapackagesTicket: CTX-271