chore(deps): update dependency storybook-dark-mode to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
storybook-dark-mode	^4.0.2 → ^5.0.0

---

Release Notes

hipstersmoothie/storybook-dark-mode (storybook-dark-mode)

v5.0.0

Compare Source

💥 Breaking Change

• Storybook V10 Compatibility #​307 (@​hipstersmoothie)

🏠 Internal

• update actions/* #​278 (@​dartess)

Authors: 2

• Andrew Lisowski (@​hipstersmoothie)
• Sergey Kozlov (@​dartess)

---

---

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 becomes conflicted, 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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[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: pnpm-lock.yaml

? Verifying lockfile against supply-chain policies (1101 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 57, reused 0, downloaded 0, added 0
Progress: resolved 61, reused 0, downloaded 1, added 0
✗ Lockfile failed supply-chain policy check (1101 entries in 7s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  vite-envs@4.7.2 was published at 2026-06-15T05:37:29.000Z, within the minimumReleaseAge cutoff (2026-06-14T12:48:26.973Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.