Bump next from 16.1.5 to 16.1.7 in /nextjs-app in the npm_and_yarn group across 1 directory#20
Conversation
Bumps the npm_and_yarn group with 1 update in the /nextjs-app directory: [next](https://github.com/vercel/next.js). Updates `next` from 16.1.5 to 16.1.7 - [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.5...v16.1.7) --- updated-dependencies: - dependency-name: next dependency-version: 16.1.7 dependency-type: direct:production dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Code Review Roast 🔥Verdict: No Issues Found | Recommendation: Merge Alright, alright, I'll give credit where it's due. This is a clean dependency bump from Dependabot. Next.js 16.1.5 → 16.1.7 with some tasty security patches including fixes for CVE-2026-27979, CVE-2026-27980, CVE-2026-27977, CVE-2026-27978, and CVE-2026-29057. That's like getting your car serviced and they also fix the squeaky brake while they're at it. I was all ready to light up this PR like a Christmas tree 🎄, but there's literally nothing to roast here. Just package.json version bumps and an updated lockfile. The diff is cleaner than my desk after my mom visits. 📊 Overall: This is exactly what a dependency update should look like — boring, mechanical, and full of security love. Merge it and move on with your life. Files Reviewed (2 files)
|
Bumps the npm_and_yarn group with 1 update in the /nextjs-app directory: next.
Updates
nextfrom 16.1.5 to 16.1.7Release notes
Sourced from next's releases.
Commits
bdf3e35v16.1.7dc98c04[backport]: fix: patch http-proxy to prevent request smuggling in rewrites (#...9023c0a[backport] Disallow Server Action submissions from privacy-sensitive contexts...36a97b9Allow blocking cross-site dev-only websocket connections from privacy-sensiti...93c3993[backport]: feat(next/image): add lru disk cache and `images.maximumDiskCache...c68d62dBackport documentation fixes for 16.1.x (#90655)5214ac1[backport]: ensure maxPostponedStateSize is always respected (#90060) (#90471)c95e357Backport/docs fixes 16.1.x (#90125)cba6144[backport] Apply server actions transform tonode_modulesin route handlers...3db9063[backport] [Cache Components] Prevent streaming fetch calls from hanging in d...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 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.