Bump next from 16.1.1 to 16.1.5 in the npm_and_yarn group across 1 directory#5
Bump next from 16.1.1 to 16.1.5 in the npm_and_yarn group across 1 directory#5dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps the npm_and_yarn group with 1 update in the / directory: [next](https://github.com/vercel/next.js). Updates `next` from 16.1.1 to 16.1.5 - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v16.1.1...v16.1.5) --- updated-dependencies: - dependency-name: next dependency-version: 16.1.5 dependency-type: direct:production dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the
Comment |
![ai-coding-guardrails[bot]](https://avatars.githubusercontent.com/in/1202546?s=60&v=4){kind=small}
There was a problem hiding this comment.
I've got 2 comments for you to consider
The PR title and description are not accurate. Here are my suggestions:
Proposed title: Security update: Bump next from 16.1.1 to 16.1.5 to address critical CVEs
Proposed description:
Updates Next.js from 16.1.1 to 16.1.5 to address critical security vulnerabilities:
Security Fixes:
- CVE-2025-59471 and CVE-2025-59472
- CVE-2026-23864
- Added maximum size limit for postponed body parsing
- Reduced next/image maximumResponseBody from 300MB to 50MB
- DoS mitigations for React Flight
Bug Fixes:
- Fixed linked list bug in LRU deleteFromLru
- Fixed relative same host redirects in node middleware
- Fixed Turbopack crash with multibyte characters in MDX files
- Performance improvements for musl-based Linux distributions (Alpine/Docker)
This is a critical security update that should be merged promptly.
List of skipped files due to configuration
Did you know Zenable also supports GitLab SaaS and self-managed?
| "@trpc/client": "^11.8.0", | ||
| "@trpc/server": "^11.8.0", | ||
| "next": "16.1.1", | ||
| "next": "16.1.5", |
There was a problem hiding this comment.
The Next.js version has been updated but eslint-config-next remains at version 16.1.1 (line 33). This version mismatch could cause compatibility issues or prevent access to updated linting rules that correspond to the new Next.js version.
| "next": "16.1.5", | |
| "next": "16.1.5", |
Why did I show this?
Category: inconsistency
Comment Quality: high
Based on general best practices
Tools used:
get_file_lines,{'file_path': 'package.json', 'start_line': 1, 'end_line': 20}get_file_lines,{'file_path': 'package.json', 'start_line': 21, 'end_line': 39}find_files,{'pattern': '**/next.config.js'}
Bumps the npm_and_yarn group with 1 update in the / directory: next.
Updates
nextfrom 16.1.1 to 16.1.5Release notes
Sourced from next's releases.
Commits
acba4a6v16.1.5e1d1fc6Add maximum size limit for postponed body parsing (#88175)500ec83fetch(next/image): reduce maximumResponseBody from 300MB to 50MB (#88588)1caaca3feat(next/image)!: addimages.maximumResponseBodyconfig (#88183)522ed84Sync DoS mitigations for React Flight8cad197[backport][cna] Ensure created app is not considered the workspace root in pn...2718661Backport/docs fixes (#89031)5333625Backport/docs fixes 16.1.5 (#88916)60de6c2v16.1.45f75d22backport: Only filter next config if experimental flag is enabled (#88733) (#...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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.