fix(deps): update dependency next to v14.2.10 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
next (source)	14.2.9 -> 14.2.10

GitHub Vulnerability Alerts

CVE-2024-46982

Impact

By sending a crafted HTTP request, it is possible to poison the cache of a non-dynamic server-side rendered route in the pages router (this does not affect the app router). When this crafted request is sent it could coerce Next.js to cache a route that is meant to not be cached and send a Cache-Control: s-maxage=1, stale-while-revalidate header which some upstream CDNs may cache as well.

To be potentially affected all of the following must apply:

• Next.js between 13.5.1 and 14.2.9
• Using pages router
• Using non-dynamic server-side rendered routes e.g. pages/dashboard.tsx not pages/blog/[slug].tsx

The below configurations are unaffected:

• Deployments using only app router
• Deployments on Vercel are not affected

Patches

This vulnerability was resolved in Next.js v13.5.7, v14.2.10, and later. We recommend upgrading regardless of whether you can reproduce the issue or not.

Workarounds

There are no official or recommended workarounds for this issue, we recommend that users patch to a safe version.

Credits

• Allam Rachid (zhero_)
• Henry Chen

---

Release Notes

vercel/next.js (next)

v14.2.10

Compare Source

---

Configuration

📅 Schedule: Branch creation - "" in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

[renovate]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
zag-nextjs	✅ Ready (Inspect)	Visit Preview	Sep 18, 2024 9:27am
zag-solid	✅ Ready (Inspect)	Visit Preview	Sep 18, 2024 9:27am
zag-svelte	✅ Ready (Inspect)	Visit Preview	Sep 18, 2024 9:27am
zag-vue	✅ Ready (Inspect)	Visit Preview	Sep 18, 2024 9:27am
zag-website	✅ Ready (Inspect)	Visit Preview	Sep 18, 2024 9:27am

[changeset-bot]

⚠️ No Changeset found

Latest commit: dc601b4

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

[pkg-pr-new]

Open in Stackblitz

@zag-js/anatomy-icons

pnpm add https://pkg.pr.new/chakra-ui/zag/@zag-js/anatomy-icons@1869

@zag-js/anatomy

pnpm add https://pkg.pr.new/chakra-ui/zag/@zag-js/anatomy@1869

@zag-js/core

pnpm add https://pkg.pr.new/chakra-ui/zag/@zag-js/core@1869

@zag-js/docs

pnpm add https://pkg.pr.new/chakra-ui/zag/@zag-js/docs@1869

@zag-js/store

pnpm add https://pkg.pr.new/chakra-ui/zag/@zag-js/store@1869

@zag-js/types

pnpm add https://pkg.pr.new/chakra-ui/zag/@zag-js/types@1869

commit: dc601b4