chore(deps): update dependency @chromatic-com/storybook to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@chromatic-com/storybook	4.1.3 → 5.2.1

---

Release Notes

chromaui/addon-visual-tests (@​chromatic-com/storybook)

v5.2.1

Compare Source

🐛 Bug Fix

• Widen peer-dependency range for storybook #​434 (@​valentinpalkovic)

Authors: 1

• Valentin Palkovic (@​valentinpalkovic)

v5.2.0

Compare Source

v5.1.2

Compare Source

🐛 Bug Fix

• Sidebar: add clear() to test provider to clear visual test statuses #​421 (@​valentinpalkovic)

Authors: 1

• Valentin Palkovic (@​valentinpalkovic)

v5.1.1

Compare Source

🐛 Bug Fix

• Fix preview errors #​416 (@​JReinhold)

Authors: 2

• Gert Hengeveld (@​ghengeveld)
• Jeppe Reinhold (@​JReinhold)

v5.1.0

Compare Source

🚀 Enhancement

• Add tool to highlight ignored elements #​411 (@​ghengeveld)

Authors: 1

• Gert Hengeveld (@​ghengeveld)

v5.0.2

Compare Source

🐛 Bug Fix

• chore: Allow 10.4 prerelease peers #​412 (@​Sidnioulz)

Authors: 2

• Steve Dodier-Lazaro (@​Sidnioulz)
• Yann Braga (@​yannbf)

v5.0.1

Compare Source

🐛 Bug Fix

• feat: Add CSF Next compatibility for definePreview addons pattern #​404 (@​jthrilly @​valentinpalkovic)
• upgrade storybook to latest #​406 (@​ndelangen)
• Main > Next sync #​407 (@​ndelangen @​chromatic-support @​ghengeveld)

Authors: 5

• @​chromatic-support
• Gert Hengeveld (@​ghengeveld)
• Joshua Melville (@​jthrilly)
• Norbert de Langen (@​ndelangen)
• Valentin Palkovic (@​valentinpalkovic)

v5.0.0

Compare Source

💥 Breaking Change

• Upgrade to Storybook 10.1 #​396 (@​ghengeveld)

🐛 Bug Fix

• Update npm version and add pull-requests permission for trusted publishing #​403 (@​ghengeveld)
• Update release workflow to use npm trusted publishing #​402 (@​ghengeveld)
• Fix: Update broken and outdated links in the addon #​397 (@​jonniebigodes)

Authors: 2

• @​jonniebigodes
• Gert Hengeveld (@​ghengeveld)

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @sozialhelden/ui@1.9.5
npm error Found: storybook@9.1.20
npm error node_modules/storybook
npm error   dev storybook@"9.1.20" from the root project
npm error
npm error Could not resolve dependency:
npm error peer storybook@"^0.0.0-0 || ^10.1.0 || ^10.1.0-0 || ^10.2.0-0 || ^10.3.0-0 || ^10.4.0-0 || ^10.5.0-0 || ^10.6.0-0" from @chromatic-com/storybook@5.2.1
npm error node_modules/@chromatic-com/storybook
npm error   dev @chromatic-com/storybook@"5.2.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-06-01T20_10_46_395Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-06-01T20_10_46_395Z-debug-0.log