Repository navigation
fix(deps): bump source-map-js to 1.2.2 for GHSA-68fv-2mgg-jv7q (release/0.8.0) - #17531
Conversation
…se/0.8.0) Backport of #17300 to release/0.8.0. The v0.8.0-insider.13 release run stopped at the production dependency audit on this advisory (high, event loop DoS through indexed source-map section offsets), so no insider build can publish from this branch until it lands. (cherry picked from commit 5edf2fe)
UX Review (Fable 5) — ✅ PASSUX-level review of UX-Verdict: PASS Nothing to check. [UX-REVIEWED] 841b224 |
Design Review (Fable 5) — ✅ PASSDesign-level review of Design-Verdict: PASS Nothing to check. [DESIGN-REVIEWED] 841b224 |
GPT 5.6 Review —
|
Opus 5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
Problem / Motivation
Goal: release/0.8.0 can publish an insider build again by clearing the high-severity
source-map-jsadvisory its release audit stops on.Backport of #17300 to release/0.8.0. The
v0.8.0-insider.13release run failed atProduction Dependency Vulnerability Gateon GHSA-68fv-2mgg-jv7q (source-map-js< 1.2.2, high), so every build and publish job after it was skipped.Why it matters
No 0.8 insider build ships until this lands, including the skill-view lock fix (#17256) and the Tool Search deferral (#17271) already on the branch.
Not a goal
What changed (motivation → approach → change)
The branch pins
source-map-js1.2.1, inside the advisory's vulnerable range.website/package-lock.jsonandsite/package-lock.jsonmovesource-map-jsto 1.2.2, the first patched release, with the registry's integrity hash. Nothing else in either lockfile changes.Backwards compatibility
Compatible: a patch release of a transitive build dependency; no API Crew uses changes.
Removes nothing: only the resolved version and its hash change.
Tests
No test change; the release workflow's production dependency audit is the check this unblocks.
Manual verification
npm view source-map-js@1.2.2 dist.integrityequals the committedintegrityin both lockfiles.Related Issues
Part of #17247
Pattern harvest
Not generalizable: a newly published upstream advisory, caught by the existing release audit as designed.
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)