Release: Patch 7.5.2

[github-actions]

This is an automated pull request that bumps the version from 7.5.1 to 7.5.2.
Once this pull request is merged, it will trigger a new release of version 7.5.2.
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:

• 🔧 Maintenance: CLI: Allow Yarn v4 in link command #24551
• ✨ Feature Request: Next.js: Support v14.0.0 #24593
• 🐛 Bug: Addon-themes: Fix globals not being set when using absolute path #24596

🍒 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 replacing the "patch:yes" label with "patch:no" on the PR and re-generate this PR.

• #24593: git cherry-pick -m1 -x 7726afc791d1741b1c90e6a62cffd6bec0031d4d

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.

Feel free to manually commit any changes necessary to this branch after you've done the last re-generation, following the Make Manual Changes section in the docs, especially if you're making changes to the changelog.

When everything above is done:

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

---

Generated changelog

7.5.2

• Addon-themes: Fix globals not being set when using absolute path - #24596, thanks @ JReinhold!
• CLI: Allow Yarn v4 in link command - #24551, thanks @ yannbf!
• Next.js: Support v14.0.0 - #24593, thanks @ nikospapcom!

[socket-security]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
next	13.5.4...14.0.0	eval	+20/-20	2.18 GB	vercel-release-bot
@next/font	13.5.6...14.0.0	None	+0/-0	2.6 MB	vercel-release-bot

[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
Uses eval	next	14.0.0	Eval Type: Function Location: dist/compiled/@babel/runtime/regenerator/index.js	@storybook/nextjs@0.0.0-use.local via code/package.json code/frameworks/nextjs/package.json

Next steps

What is eval?

Package uses eval() which is a dangerous function. This prevents the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use eval, since this could potentially execute any code.

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 foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore next@14.0.0