chore(deps): bump next from 16.2.2 to 16.2.6#264
Conversation
Bumps [next](https://github.com/vercel/next.js) from 16.2.2 to 16.2.6. - [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.2.2...v16.2.6) --- updated-dependencies: - dependency-name: next dependency-version: 16.2.6 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 5f63995. Configure here.
| "@prismicio/client": "^7.21.7", | ||
| "@prismicio/react": "*", | ||
| "next": "16.2.2", | ||
| "next": "^16.2.6", |
There was a problem hiding this comment.
Version specifier mismatch between package.json and lockfile
Low Severity
The package-lock.json records "next": "^16.2.6" (with caret) for the e2e-projects/nextjs workspace, but the corresponding package.json specifies an exact version "next": "16.2.6" (no caret). The previous version was consistently pinned in both files as "16.2.2". This mismatch means the lockfile no longer accurately reflects the package.json constraint, which could cause unexpected version resolution behavior on future npm install runs.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 5f63995. Configure here.
Bumps next from 16.2.2 to 16.2.6.
Release notes
Sourced from next's releases.
... (truncated)
Commits
ee6e79bv16.2.6afa053dTurbopack: Match proxy matchers with webpack implementation (#93594)97a154eTurbopack: Fix middleware matcher suffix (#93590)83899bc[backport] Disable build caches for production/staging/force-preview deploys ...7b222b9[backport][test] Pin package manager to patch versions (#93595)a8dc24f[backport] Turbopack: more strict vergen setup (#93587)766148fv16.2.50dd9483fix: add explicit checks for RSC header (#83) (#98)d166096fix proxy matching for segment prefetch URLs (#89) (#96)9d50c0bStrip next-resume header from incoming requests (#92)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for next since your current version.
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 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)You can disable automated security fix PRs for this repo from the Security Alerts page.
Need help on this PR? Tag
@codesmithwith what you need.Note
Low Risk
Low risk patch-level dependency update, but it changes the Next.js runtime/toolchain (including SWC binaries) which could affect e2e app builds or routing behavior.
Overview
Bumps the
e2e-projects/nextjsworkspace fromnext@16.2.2tonext@16.2.6.Updates
package-lock.jsonto pull innext@16.2.6and matching@next/*packages/SWC platform binaries (and adjusts the locked Next.js version range for the workspace).Reviewed by Cursor Bugbot for commit 5f63995. Bugbot is set up for automated code reviews on this repo. Configure here.