🐛 Bump js-yaml to 4.3.2 and Storybook to 10.6.2, drop unused smol-toml
Merged
MI
7d ago+465+465+012345678901234567890123456789-156-156-012345678901234567890123456789
Security dependency fix. Nothing else changes.
| Package | From | To | Advisories cleared |
|---|---|---|---|
| js-yaml (lockfile, transitive via electron-builder / electron-updater) | 4.3.0 | 4.3.2 | GHSA-2883-xcg3-v3hh (CVE-2026-84375), GHSA-5p4m-2wfm-xmqj |
js-yaml (pinned in desktop-release.yml and desktop-release-demo.yml for merge-win-update-manifest.cjs) | 4.1.0 | 4.3.2 | GHSA-2883-xcg3-v3hh, GHSA-52cp-r559-cp3m, GHSA-5p4m-2wfm-xmqj, GHSA-h67p-54hq-rp68, GHSA-mh29-5h37-fv8m |
| storybook + @storybook/* (dev only, desktop + shared) | 10.5.7 | 10.6.2 | GHSA-f2ph-cmg5-wxc8 (CVE-2026-114125), GHSA-px85-f4q5-jh77 (CVE-2026-114126) |
| smol-toml (direct dep of packages/desktop) | ^1.6.1 | removed | n/a (unused: no imports anywhere) |
Notes:
- Each target is the smallest version that fixes the advisory (js-yaml patch bump, Storybook 10.5 to 10.6 minor, no 10.5.x fix exists). Both are older than 14 days (js-yaml 4.3.2: 2026-08-26, Storybook 10.6.2: 2026-10-12) and match 0 advisories in a local copy of the OSV npm dump. Publishers are unchanged (js-yaml: same maintainer account; Storybook: same GitHub Actions trusted publisher with provenance). No 2026 compromise reports found for either.
- The lockfile was regenerated with npm (
npm install --package-lock-only --before=2026-10-13, thennpm update js-yaml), so every re-resolved transitive is also at least 14 days old. A few Storybook transitives moved with it (react-docgen, resolve, @testing-library/user-event, oxc-resolver). The new lock introduces no new OSV matches. - smol-toml 1.7.0 stays in the tree as a transitive dev dependency of knip, and still matches GHSA-7w5x-hrqm-74c2 and GHSA-r4xh-jqrq-34v2. That needs a knip bump and is out of scope here.
Test plan
-
npm cifrom root - shared:
typecheck,lint,format:check,knip,test(62 passed),build,build-storybook - desktop:
typecheck,test:coverage(210 passed),build - root:
pinned-refs:check,version:check - desktop
build-storybookfails here, but it also fails onmainin this sandbox (unresolvedpackages/packages/sharedpath). It is not part of desktop CI. - Next release run: confirm the Windows
latest.ymlmerge step still works with js-yaml 4.3.2
Generated by Claude Code
Summary by cubic
Security dependency bump: js-yaml to 4.3.2 and Storybook to 10.6.2 clear multiple advisories, and the unused direct smol-toml dependency is dropped from packages/desktop. No behavior changes.
Notes
- js-yaml is bumped in the lockfile (transitive via electron-builder/electron-updater) and the pinned version in
desktop-release.yml/desktop-release-demo.yml, clearing GHSA-2883-xcg3-v3hh, GHSA-5p4m-2wfm-xmqj, GHSA-52cp-r559-cp3m, GHSA-h67p-54hq-rp68, and GHSA-mh29-5h37-fv8m. - Storybook and
@storybook/*move 10.5.7 → 10.6.2 (dev only), clearing GHSA-f2ph-cmg5-wxc8 and GHSA-px85-f4q5-jh77. smol-tomlremains in the tree as a transitive dev dependency of knip and still matches GHSA-7w5x-hrqm-74c2 and GHSA-r4xh-jqrq-34v2; that requires a knip bump and is out of scope here.