Update nextjs monorepo to v14.2.10

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@next/env (source)	14.2.9 -> 14.2.10
@next/eslint-plugin-next (source)	14.2.9 -> 14.2.10
@next/polyfill-module (source)	14.2.9 -> 14.2.10
@next/polyfill-nomodule (source)	14.2.9 -> 14.2.10
@next/react-refresh-utils (source)	14.2.9 -> 14.2.10

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

vercel/next.js (@​next/env)

v14.2.10

Compare Source

vercel/next.js (@​next/eslint-plugin-next)

v14.2.10

Compare Source

vercel/next.js (@​next/polyfill-module)

v14.2.10

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• Remove invalid fallback revalidate value (https://github.com/vercel/next.js/pull/69990)
• Revert server action optimization (https://github.com/vercel/next.js/pull/69925)
• Add ability to customize Cache-Control (#​69802)

Credits

Huge thanks to @​huozhi and @​ijjk for helping!

---

Configuration

📅 Schedule: 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 these updates 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]

⚠️ 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

 ERROR  Expected double-quoted property name in JSON at position 7388 while parsing '{  "name": "nextjs-project",  "version' in /tmp/renovate/repos/github/X-oss-byte/Canary-nextjs/package.json 

  183 |     "playwright-chromium": "1.38.1",
  184 |     "plop": "3.0.5",
> 185 |  01-30-Add_test_for_issue_45393
      |  ^
  186 |     "postcss-nested": "4.2.3",
  187 |     "postcss-pseudoelements": "5.0.0",
  188 |     "postcss-short-size": "4.0.0",

For help, run: pnpm help install

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 19750cd

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