Update all of nextjs 16.0.10 → 16.1.0 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ eslint-config-next (16.0.10 → 16.1.0)

Sorry, we couldn't find anything useful about this release.

✳️ next (16.0.10 → 16.1.0) · Repo

Release Notes

16.1.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[coderabbitai]

Walkthrough

The changes update dependency versions in two package.json files. In playgrounds/nextjs/package.json and playgrounds/v3/package.json, the next package is upgraded from ^16.0.10 to ^16.1.0, and eslint-config-next is upgraded from ^16.0.10 to ^16.1.0. No other dependencies are modified, and there are no changes to project logic, control flow, or scripts. No alterations to exported or public declarations are present.

Pre-merge checks

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: updating Next.js from version 16.0.10 to 16.1.0 across multiple files, with appropriate version designation.
Description check	✅ Passed	The description is related to the changeset, providing dependency update details, release notes references, and commit information for the Next.js version bump.

---

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 543da3f and 2a0963a.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (2)

• playgrounds/nextjs/package.json (2 hunks)
• playgrounds/v3/package.json (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)

• GitHub Check: Linux
• GitHub Check: Windows
• GitHub Check: macOS
• GitHub Check: Linux / postcss
• GitHub Check: Linux / oxide
• GitHub Check: Linux / webpack
• GitHub Check: Linux / vite
• GitHub Check: Linux / cli
• GitHub Check: Linux / upgrade

🔇 Additional comments (1)

playgrounds/v3/package.json (1)

12-12: LGTM! Consistent with the nextjs playground.

The dependency upgrades match those in playgrounds/nextjs/package.json, maintaining version consistency across both playgrounds.

Also applies to: 23-23

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

The specified eslint-config-next version does not exist; this is a critical version mismatch.

Next.js 16.1.0 exists and is the latest stable version, and Next.js versions 16.0.0 – 16.0.6 are affected by CVE-2025-55182, making 16.1.0 safe from this critical vulnerability.

However, eslint-config-next's latest stable version is 16.0.10, published 6 days ago. The eslint-config-next 16.1.0 version does not exist as a stable release. If the package.json specifies "eslint-config-next": "^16.1.0", this will fail to resolve during installation.

Correct the dependency to use eslint-config-next@^16.0.10 to match the actual available version, or wait for eslint-config-next 16.1.0 to be released.

🤖 Prompt for AI Agents

In playgrounds/nextjs/package.json around line 14, the package.json references a
non-existent eslint-config-next version (^16.1.0) which will fail to resolve;
update the eslint-config-next dependency to the latest published stable version
by changing it to ^16.0.10 (or another available released version) so installs
succeed, ensuring the version string matches the actual released
eslint-config-next package.

[depfu]

Sorry, but the merge failed with:

At least 1 approving review is required by reviewers with write access.