build(deps): bump next from 16.0.9 to 16.0.10

[dependabot]

Bumps next from 16.0.9 to 16.0.10.

Release notes

Sourced from next's releases.

v16.0.10

Please see the Next.js Security Update for information about this security patch.

Commits

• 581dee6 v16.0.10
• 9a0dc9c Backport facebook/react#35351 for 16.0.9 (#87085)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

---

Summary by cubic

Upgrade Next.js from 16.0.9 to 16.0.10 to apply the latest security patch. Only dependency files changed; no app code updates.

• Dependencies
  • Bumped next to 16.0.10 and refreshed pnpm lockfile.

^{Written for commit 0291f6c. Summary will update automatically on new commits.}

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
ever-works-website-template	Ready	Preview	Comment	Dec 12, 2025 5:27pm

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Important

Review skipped

Bot user detected.

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.

---

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

[cubic-dev-ai]

No issues found across 2 files

[greptile-apps]

Greptile Overview

Greptile Summary

Security patch updating Next.js from 16.0.9 to 16.0.10 to address vulnerabilities disclosed in the Next.js Security Update (2025-12-11). The update backports a React fix (facebook/react#35351) related to security improvements.

• Both package.json and pnpm-lock.yaml properly updated
• All transitive dependencies correctly resolved in lockfile
• Version change is a patch update with no breaking changes expected
• Complies with custom rule requiring both manifest and lockfile updates for dependency PRs

Confidence Score: 5/5

• This PR is safe to merge after running tests - critical security patch with minimal risk
• Score of 5 reflects that this is a patch-level security update with no breaking changes, properly updates both manifest and lockfile per custom rules, addresses known security vulnerabilities disclosed by Vercel, and follows standard Dependabot practices. The only requirement before merge is confirming tests pass.
• No files require special attention - standard dependency update

Important Files Changed

File Analysis

Filename	Score	Overview
package.json	5/5	Updated Next.js from 16.0.9 to 16.0.10 (security patch)
pnpm-lock.yaml	5/5	Lockfile updated with Next.js 16.0.10 and transitive dependency resolutions

Sequence Diagram

sequenceDiagram
    participant D as Dependabot
    participant R as Repository
    participant P as package.json
    participant L as pnpm-lock.yaml
    participant N as Next.js 16.0.10
    
    D->>R: Detect security vulnerability in Next.js 16.0.9
    D->>P: Update Next.js version to ^16.0.10
    D->>L: Resolve dependencies and update lockfile
    L->>N: Fetch Next.js 16.0.10 with security patch
    L->>L: Update transitive dependencies (@next/env, @next/swc-*, etc)
    L->>L: Update peer dependencies (@sentry/nextjs, next-auth, etc)
    N-->>R: Security patch applied (React fix #35351)
    R-->>D: PR created for review and testing

Loading

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

style: Check that all tests pass before merging this security update

Context Used: Rule from dashboard - When updating dependencies via automated PRs (like Dependabot), ensure the package.json file is expl... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: package.json
Line: 110:110

Comment:
**style:** Check that all tests pass before merging this security update

**Context Used:** Rule from `dashboard` - When updating dependencies via automated PRs (like Dependabot), ensure the package.json file is expl... ([source](https://app.greptile.com/review/custom-context?memory=d1ffbb9b-c4e0-4fc6-bae7-688b0ae84515))

How can I resolve this? If you propose a fix, please make it concise.