[Snyk] Security upgrade next from 14.2.14 to 15.0.8

[decause-gov]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-NEXT-15921797	168

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

[decause-gov]

The upgrade from Next.js v14.2.14 to v15.0.8 is a major version change that introduces significant breaking changes requiring code modifications and careful review.

Key Breaking Changes:

• New Caching Default: fetch requests, GET Route Handlers, and client-side navigations are no longer cached by default. This is a fundamental shift from previous versions where caching was automatic. You must now explicitly opt-in to caching where needed (e.g., using fetch(..., { cache: 'force-cache' })). This change could significantly impact application performance and load if not addressed.

• Asynchronous Request APIs: Several previously synchronous APIs are now asynchronous and must be awaited. This affects:

  • cookies()
  • headers()
  • draftMode()
  • params and searchParams in pages and layouts.

  Example Migration:
  // Before const cookieStore = cookies() // After const cookieStore = await cookies()

• React 19 Upgrade: Next.js 15 now requires React 19. While Next.js provides backward compatibility for the Pages Router with React 18, the App Router uses React 19 RC. This may cause peer dependency conflicts with other libraries that have not yet been updated for React 19.

• Minimum Node.js Version: The minimum required Node.js version has been updated to 18.18.0.

Recommendation:
This is a high-risk upgrade. It is strongly recommended to use the provided codemods to automate parts of the migration (npx @next/codemod@canary upgrade latest). Thoroughly test your application after upgrading, paying close attention to caching behavior, data fetching, and any functions that rely on request-specific APIs. Verify that third-party dependencies are compatible with React 19 before merging.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.