-
Notifications
You must be signed in to change notification settings - Fork 11
chore(deps): bump next from 15.1.3 to 16.0.1 #265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Bumps [next](https://github.com/vercel/next.js) from 15.1.3 to 16.0.1. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v15.1.3...v16.0.1) --- updated-dependencies: - dependency-name: next dependency-version: 16.0.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
main-website | 3b9a442 | Oct 28 2025, 11:23 PM |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Greptile Overview
Greptile Summary
This PR upgrades Next.js from 15.1.3 to 16.0.1, a major version bump that includes numerous bug fixes and improvements.
Key changes in Next.js 16.0.1:
- React upgrade and improved Server Actions handling
- Fixed proxy detection on Windows
- Enhanced prefetch functionality (restored
prefetch={true}) - Improved image dependency handling
- Better TypeScript type generation
Compatibility concerns:
@next/third-partiesremains at 15.1.3 (not upgraded alongside Next.js)eslint-config-nextremains at 15.1.3 (may need updating)- Project uses
@opennextjs/cloudflarefor deployment, which should be tested with Next.js 16 - Experimental
staleTimesfeature in config should be verified to work with v16
Testing recommendations:
- Verify build completes successfully with new version
- Test Cloudflare deployment with
@opennextjs/cloudflare - Ensure all Next.js Image components render correctly (16 usages found)
- Validate Server Actions still function properly (3 files with
"use server") - Check ESLint configuration compatibility
Confidence Score: 3/5
- This PR requires testing due to major version upgrade and dependency version mismatches
- Score reflects the major version jump (15→16) with companion packages still on v15, and deployment dependencies that need compatibility verification with Next.js 16
- Verify
package.json- companion Next.js packages should be updated to v16 for consistency
Important Files Changed
File Analysis
| Filename | Score | Overview |
|---|---|---|
| package.json | 3/5 | Updated Next.js from 15.1.3 to 16.0.1 (major version bump), but @next/third-parties and eslint-config-next remain on 15.1.3 |
| bun.lock | 4/5 | Lock file updated to reflect Next.js 16.0.1 dependencies |
Sequence Diagram
sequenceDiagram
participant Dev as Developer
participant Dep as Dependabot
participant PKG as package.json
participant Lock as bun.lock
participant Next as Next.js 16.0.1
Dep->>PKG: Update next: 15.1.3 → 16.0.1
Dep->>Lock: Resolve & update dependencies
Dev->>PKG: Review version compatibility
Note over PKG: @next/third-parties: 15.1.3<br/>eslint-config-next: 15.1.3<br/>next: 16.0.1
Dev->>Next: Test with existing codebase
Note over Next: Major version upgrade<br/>React 19 support<br/>New cache APIs<br/>Proxy feature updates
Additional Comments (2)
1 file reviewed, 2 comments



Bumps next from 15.1.3 to 16.0.1.
Release notes
Sourced from next's releases.
... (truncated)
Commits
e08402bv16.0.151d9631Upgrade React from6160773f-20251023tob4455a6e-20251027(#85464)163fc17v16.0.1-canary.6a986e17Fix crash when suspending in Components usinguseActionQueue(#85459)4067214Turbopack: correctly trace files with npm (#85323)976a222[test] Ensure we can toggle the DevTools menu while status indicators are act...b95dbe6fix: Proxy not picked up on Windows (#85443)b0837e0[test] Exclude likely Next.js internal Components from component stacks in Re...456d8e7fix: ensure req.query is writable (#81573)0b6fe15[test] Exclude Next.js internal stack frames from cache-component-error CLI o...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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)