This repository was archived by the owner on Jan 25, 2026. It is now read-only.
chore(deps): bump next from 15.1.3 to 16.0.0#264
Closed
dependabot[bot] wants to merge 1 commit intomasterfrom
Closed
chore(deps): bump next from 15.1.3 to 16.0.0#264dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot[bot] wants to merge 1 commit intomasterfrom
Conversation
Bumps [next](https://github.com/vercel/next.js) from 15.1.3 to 16.0.0. - [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.0) --- updated-dependencies: - dependency-name: next dependency-version: 16.0.0 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 | a4e4b83 | Oct 22 2025, 11:21 PM |
|
Contributor
There was a problem hiding this comment.
Greptile Overview
Summary
This PR upgrades Next.js from version 15.1.3 to 16.0.0, a major version upgrade that includes numerous core improvements and breaking changes.
Key Changes:
- Next.js upgraded to 16.0.0 with React 19 support and enhanced Turbopack integration
- Flat ESLint config as default in
@next/eslint-plugin-next - Improved development performance and TypeScript 5.9.2 support
- Native TypeScript config support with
next.config.mts
Compatibility Concerns:
@next/third-partiesandeslint-config-nextremain at 15.1.3 - verify compatibility with Next.js 16- Project uses legacy
.eslintrc.jsonformat - Next.js 16 defaults to flat config - Edge runtime used in root layout - ensure compatibility with Next.js 16 changes
Confidence Score: 4/5
- This PR is relatively safe to merge with minor version alignment checks needed
- Score reflects that this is a clean dependency upgrade by Dependabot with no code changes, but there are version mismatches in related Next.js packages (@next/third-parties and eslint-config-next remain at 15.1.3) that should be verified for compatibility. The codebase uses standard Next.js patterns with edge runtime and next-intl plugin that are well-supported in Next.js 16
- Verify that @next/third-parties and eslint-config-next at version 15.1.3 are compatible with Next.js 16.0.0
Important Files Changed
File Analysis
| Filename | Score | Overview |
|---|---|---|
| package.json | 4/5 | Upgrades Next.js from 15.1.3 to 16.0.0 - major version bump with potential breaking changes |
| bun.lock | 5/5 | Lockfile updated automatically by Bun package manager - reflects dependency resolution |
Sequence Diagram
sequenceDiagram
participant Dev as Developer
participant Dep as Dependabot
participant PM as Package Manager (Bun)
participant Next as Next.js Runtime
participant App as Application
Dep->>PM: Detect Next.js 16.0.0 available
Dep->>PM: Update package.json (15.1.3 → 16.0.0)
PM->>PM: Resolve dependencies
PM->>PM: Update bun.lock
Note over PM: Maintains @next/third-parties@15.1.3<br/>and eslint-config-next@15.1.3
Dev->>PM: bun install
PM->>Next: Install Next.js 16.0.0
PM->>App: Install React 19.1.0
Dev->>Next: npm run dev/build
Next->>App: Initialize with Turbopack
Next->>App: Apply edge runtime config
Next->>App: Load next-intl plugin
App->>Next: Render with React 19
Note over Dev,App: Potential compatibility checks needed:<br/>- @next/third-parties version mismatch<br/>- eslint-config-next version mismatch<br/>- Edge runtime compatibility
Additional Comments (2)
1 file reviewed, 2 comments
Contributor
Author
|
Superseded by #265. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Bumps next from 15.1.3 to 16.0.0.
Release notes
Sourced from next's releases.
... (truncated)
Commits
950609fv16.0.0fcc3157v16.0.0-canary.19c0b086cv16.0.0-canary.18f770793logger: skip logging full element (#85194)074262bOnly allow node runtime in proxy (#85139)47ceda3[cache components] persist cache bypass UI until it's disabled (#85190)b66c1d6Remove layout-router sticky/fixed debug warning (#85193)96754b6Tweaks to blocking route error message (#85191)48bb490docs: upgrade from 15 to 16 (#85176)9b34b65[upgrade] Version gate adding--turbopackflag (#85180)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)