Context
Dependabot opened #360 to bump just `@storybook/addon-themes` from 9.1.20 → 10.4.6. The peer dependency on the rest of `@storybook/*` is pinned to ^9.x, so the major-version mismatch fails both:
- `Web — Storybook build (design system v2)`
- `Storybook visual diff`
A point bump of a single addon to a different major is not safe. We need to migrate the entire Storybook installation at once.
What's needed
- Bump every `@storybook/*` package in `apps/web/package.json` to 10.x (currently pinned in the 9.1.x range).
- Run the Storybook 10 codemod: `pnpm dlx storybook@latest upgrade --yes`.
- Verify Storybook builds: `pnpm --filter @aisoc/web storybook:build`.
- Refresh the 33 visual-regression snapshots at `apps/web/src/test/snapshots/storybook-snapshots.test.tsx.snap` if any have legitimately changed; eyeball-check the new ones.
- Verify CI gates pass:
- `Web — Storybook build (design system v2)`
- `Storybook visual diff`
- Update `AISOC_V8_PROGRESS.md` T3.8 note if any of the per-primitive stories changed shape.
Why this is a separate issue, not just a re-open of #360
We deliberately want a single PR that owns the whole 9 → 10 migration so:
- All the snapshot diff churn lives in one PR (reviewable in one shot).
- The Dependabot grouping in `.github/dependabot.yml` doesn't need to keep `addon-themes` quarantined from the rest of the Storybook family.
- If we need to bisect a regression later, it's bisectable against one commit.
Once a maintainer has time, drop the Storybook 9.x pin and re-do the bump end-to-end. Until then, all `@storybook/*` Dependabot PRs should be closed with a redirect to this issue.
Accept criteria
- All `@storybook/*` packages in `apps/web/package.json` on 10.x.
- Both Storybook CI gates green.
- 33 visual-regression snapshots either unchanged or intentionally regenerated.
Context
Dependabot opened #360 to bump just `@storybook/addon-themes` from 9.1.20 → 10.4.6. The peer dependency on the rest of `@storybook/*` is pinned to ^9.x, so the major-version mismatch fails both:
A point bump of a single addon to a different major is not safe. We need to migrate the entire Storybook installation at once.
What's needed
Why this is a separate issue, not just a re-open of #360
We deliberately want a single PR that owns the whole 9 → 10 migration so:
Once a maintainer has time, drop the Storybook 9.x pin and re-do the bump end-to-end. Until then, all `@storybook/*` Dependabot PRs should be closed with a redirect to this issue.
Accept criteria