Release: Patch 7.0.24

[github-actions]

This is an automated pull request that bumps the version from 7.0.23 to 7.0.24.
Once this pull request is merged, it will trigger a new release of version 7.0.24.
If you're not a core maintainer with permissions to release you can ignore this pull request.

To do

Before merging the PR, there are a few QA steps to go through:

• Add the "freeze" label to this PR, to ensure it doesn't get automatically forced pushed by new changes.
• Add the "ci:daily" label to this PR, to trigger the full test suite to run on this PR.

And for each change below:

1. Ensure the change is appropriate for the version bump. E.g. patch release should only contain patches, not new or de-stabilizing features. If a change is not appropriate, revert the PR.
2. Ensure the PR is labeled correctly with one of: "BREAKING CHANGE", "feature request", "bug", "maintenance", "dependencies", "documentation", "build", "unknown".
3. Ensure the PR title is correct, and follows the format "[Area]: [Summary]", e.g. "React: Fix hooks in CSF3 render functions". If it is not correct, change the title in the PR.
   • Areas include: React, Vue, Core, Docs, Controls, etc.
   • First word of summary indicates the type: “Add”, “Fix”, “Upgrade”, etc.
   • The entire title should fit on a line

This is a list of all the PRs merged and commits pushed directly to next, that will be part of this release:

• 🐛 Bug: CLI: Parse pnp paths in storybook metadata #23199
• 🔧 Maintenance: Svelte: Support v4 #22905
• 📦 Dependencies: Dependencies: Pin file-system-cache to 2.3.0 #23221
• 📝 Documentation: Docs: Remove "(deprecated)" & "(required)" from headings #23060
• 🏗️ Build: Build: Fix workflow link in release PR description #23116
• 🏗️ Build: Build: Don't auto-trigger CI on release PRs #23198
• 🏗️ Build: Build: Add benchmark task #22161
• 📝 Documentation: Added @ import to Webpack config, without needing a package #23020
• 📝 Documentation: added information that jest is not globally available #22876
• 🏗️ Build: Release tooling: Label merges as "release" #23219

🍒 Manual cherry picking needed!

The following pull requests could not be cherry-picked automatically because it resulted in merge conflicts.
For each pull request below, you need to either manually cherry pick it, or discard it by removing the "patch" label from the PR and re-generate this PR.

• #23060: git cherry-pick -m1 -x 0fd56650cd052f52d7dd114bebd3c73440a06b35
• #22161: git cherry-pick -m1 -x 162ba43c23181a0e3d4da5ac1e68c5c1f68118d7
• #23199: git cherry-pick -m1 -x 4f7cd07e9b4e2da6b347c36de033df8463108167
• #22905: git cherry-pick -m1 -x 96b838b83afedb0bbde39aa2ce294c556e544f23
• #23221: git cherry-pick -m1 -x 54142ad20abb4a48e157b421d31fbde0e0bd1ffa
• #23219: git cherry-pick -m1 -x 156bd6e88a6746e277cb87db9e0a8b9db8459b55

If you've made any changes doing the above QA (change PR titles, revert PRs), manually trigger a re-generation of this PR with this workflow and wait for it to finish. It will wipe your progress in this to do, which is expected.

When everything above is done:

• Merge this PR
• Follow the run of the publish action

---

Generated changelog

7.0.24

• CLI: Parse pnp paths in storybook metadata - #23199, thanks @ yannbf!
• Dependencies: Pin file-system-cache to 2.3.0 - #23221, thanks @ JReinhold!
• Svelte: Support v4 - #22905, thanks @ JReinhold!

[socket-security]

New and updated dependency changes detected. Learn more about Socket for GitHub ↗︎

Packages		Version	New capabilities	Transitives1	Size	Publisher
svelte-check	⬆️	2.10.3...3.4.4	None	+2/-5	8.96 MB	svelte-language-tools-deploy

🚮 Removed packages: @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected], @storybook/[email protected]

Footnotes

1. https://docs.socket.dev ↩

[github-actions]

	Fails
🚫	PR is not labeled with one of: ["cleanup","BREAKING CHANGE","feature request","bug","documentation","maintenance","build","dependencies"]

Generated by 🚫 dangerJS against 1eec3cd

[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.

Issue	Package	Version	Note	Source
Install scripts	svelte-preprocess	5.0.4	Install script: postinstall Source: echo "[svelte-preprocess] Don't forget to install the preprocessors packages that will be used: sass, stylus, less, postcss & postcss-load-config, coffeescript, pug, etc..."	code/renderers/svelte/package.json via [email protected]

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 package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore [email protected]