chore(deps): update storybook monorepo to v8.1.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@storybook/addon-essentials (source)	8.1.0 -> 8.1.1
@storybook/addon-interactions (source)	8.1.0 -> 8.1.1
@storybook/addon-links (source)	8.1.0 -> 8.1.1
@storybook/addon-onboarding (source)	8.1.0 -> 8.1.1
@storybook/addon-themes (source)	8.1.0 -> 8.1.1
@storybook/blocks (source)	8.1.0 -> 8.1.1
@storybook/react (source)	8.1.0 -> 8.1.1
@storybook/react-vite (source)	8.1.0 -> 8.1.1
@storybook/test (source)	8.1.0 -> 8.1.1
storybook (source)	8.1.0 -> 8.1.1

---

Release Notes

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

v8.1.1

Compare Source

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

v8.1.1

Compare Source

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

v8.1.1

Compare Source

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

v8.1.1

Compare Source

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

v8.1.1

Compare Source

• Docgen: Only add react-docgen info when a component is defined in the file - #​26967, thanks @​glenjamin!
• Docs: Fix MDX Stories block tag-filtering behavior - #​27144, thanks @​shilman!
• Docs: Fix Subtitle block when no of prop passed - #​27147, thanks @​JReinhold!
• Next.js: Add typing for NextImage to main framework options type - #​27105, thanks @​valentinpalkovic!
• Next.js: Avoid conflicts with the raw loader - #​27093, thanks @​seanparmelee!
• Types: Fix typing for main.framework/builder fields - #​27088, thanks @​valentinpalkovic!

storybookjs/storybook (@​storybook/blocks)

v8.1.1

Compare Source

storybookjs/storybook (@​storybook/react)

v8.1.1

Compare Source

storybookjs/storybook (@​storybook/react-vite)

v8.1.1

Compare Source

storybookjs/storybook (@​storybook/test)

v8.1.1

Compare Source

storybookjs/storybook (storybook)

v8.1.1

Compare Source

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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 these updates again.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[changeset-bot]

⚠️ No Changeset found

Latest commit: aaaf509

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (main@b3cdc15). Click here to learn what that means.

Additional details and impacted files

@@          Coverage Diff           @@
##             main    #883   +/-   ##
======================================
  Coverage        ?   4.06%           
======================================
  Files           ?      40           
  Lines           ?    3150           
  Branches        ?      43           
======================================
  Hits            ?     128           
  Misses          ?    3022           
  Partials        ?       0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Install scripts	npm/@swc/core@1.5.5	Install script: postinstall Source: node postinstall.js	orphan: npm/@swc/core@1.5.5

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/@swc/core@1.5.5