[Snyk] Security upgrade next from 15.4.2 to 16.1.5

[A222moq3e]

Snyk has created this PR to fix 2 vulnerabilities in the pnpm dependencies of this project.

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

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

---

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

---

Note

Medium Risk
Upgrades Next.js across a major version, which can introduce breaking framework/runtime changes at build and request handling time. The lockfile is not updated in this PR, so installs may still resolve to the old version until pnpm-lock.yaml is regenerated.

Overview
Updates the next dependency in package.json from ^15.2.3 to ^16.1.5 (Snyk-driven security upgrade).

No other dependencies or code are changed, and pnpm-lock.yaml is not updated as part of this PR.

^{Written by Cursor Bugbot for commit d42faeb. This will update automatically on new commits. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
tedx	Error		Jan 28, 2026 9:26pm

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

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

• 🔍 Trigger a full review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

This is the final PR Bugbot will review for you during this billing cycle

Your free Bugbot reviews will reset on February 7

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

eslint-config-next version not updated with Next.js upgrade

Medium Severity

Upgrading next from version 15 to 16 without also upgrading eslint-config-next (still at ^15.2.3 in devDependencies) causes a version mismatch. The eslint-config-next package is versioned to match its corresponding Next.js version, and using mismatched versions can lead to linting errors, unrecognized Next.js 16 APIs, or incorrect deprecation warnings during builds and CI runs.