[Snyk] Security upgrade next from 15.4.11 to 15.5.10

[ykstorm]

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

Snyk changed the following file(s):

• docs-site/package.json
• docs-site/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-NEXT-15104645	624

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

[ykstorm]

This is a minor version upgrade that introduces new features, performance improvements, and deprecation warnings for changes coming in Next.js 16. There are no immediate breaking changes, but one deprecation requires attention.

Key Changes:

• next lint Deprecation: The next lint command is now deprecated and will be removed in Next.js 16. Projects should transition to calling ESLint or another linter like Biome directly. A codemod is available to help automate this migration: npx @next/codemod@latest next-lint-to-eslint-cli .
• New Features: This release stabilizes the Node.js middleware runtime, introduces Turbopack for production builds (beta), and adds significant TypeScript improvements like stable typed routes.
• Deprecation Warnings for Next.js 16: You will see new warnings in development and build logs for features that will be removed in Next.js 16, such as the legacyBehavior prop on next/link and built-in AMP support.

Recommendation:
The upgrade is low risk. The primary action required is to plan the migration away from next lint to a direct ESLint or Biome setup to avoid issues when upgrading to Next.js 16 in the future.

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

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: aedd035c-33f5-4951-8496-08edcdccb29f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch snyk-fix-e305af45c14067afb92b6b3da9811768

---

_{Comment @coderabbitai help to get the list of available commands.}