[ferrlabs-renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@storybook/addon-a11y (source)	10.6.3 → 10.6.4
@storybook/addon-docs (source)	10.6.3 → 10.6.4
@storybook/addon-themes (source)	10.6.3 → 10.6.4
@storybook/angular (source)	10.6.3 → 10.6.4
storybook (source)	10.6.3 → 10.6.4

---

Release Notes

storybookjs/storybook (@​storybook/addon-a11y)

v10.6.4

Compare Source

• Core: Skip TypeScript loader hook registration under Jest - #​36790, thanks @​obvious-autobuild!

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[ferrfleet-interne]

Storybook 10.6.3 to 10.6.4 is a patch bump, and the change is confined to pnpm-lock.yaml. I did not read the upstream 10.6.4 release notes, so I can't say what changed in the patch itself. Every @storybook/* package and storybook moved together, and the storybook peer ranges match.

The relock also dropped the duplicate webpack@5.111.1 (with watchpack@2.5.2, css-loader, minimizer-webpack-plugin). Everything now resolves to webpack@5.112.0, which was already in the tree for @angular-devkit/build-angular. That's a simplification, not a risk.

CI was still running when I looked (Typecheck, Storybook accessibility, osv-scanner and others pending). Snyk, gitleaks, zizmor, sign-off and the PR title check had passed. I did not verify the Storybook build or the a11y job, so a failure there would need a human look.