chore(deps): bump next from 15.3.6 to 16.1.6#842
chore(deps): bump next from 15.3.6 to 16.1.6#842dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
dependabot
bot
added
dependencies
dependabot
bot
requested review from
meryldakin and
thomaswhyyou
and removed request for
a team
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/next-16.1.6
branch
from
f19fcf6 to
9728648
Compare
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/next-16.1.6
branch
from
9728648 to
3f841f0
Compare
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
| "@knocklabs/react": "0.11.0", | ||
| "jsonwebtoken": "^9.0.2", | ||
| "next": "15.3.6", | ||
| "next": "16.1.6", |
There was a problem hiding this comment.
Lint scripts break after Next major upgrade
Medium Severity
Upgrading next to 16.1.6 leaves lint scripts using next lint, but that command was removed in Next 16. In these example apps, yarn lint now fails immediately, so lint checks and related CI jobs stop working after this dependency bump.
Additional Locations (2)
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/next-16.1.6
branch
from
3f841f0 to
a86f267
Compare
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/next-16.1.6
branch
from
a86f267 to
316c838
Compare
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/next-16.1.6
branch
from
316c838 to
5bd1de4
Compare
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/next-16.1.6
branch
from
5bd1de4 to
fc352f4
Compare
| "@knocklabs/react": "0.11.3", | ||
| "jsonwebtoken": "^9.0.2", | ||
| "next": "15.3.6", | ||
| "next": "16.1.6", |
There was a problem hiding this comment.
Major version mismatch between next and eslint-config-next
Medium Severity
Bumping next to 16.1.6 while eslint-config-next remains at 15.4.6 creates a cross-major-version mismatch. The eslint-config-next package is designed to match the major version of next and may produce incorrect lint results, false warnings, or fail to detect new patterns introduced in Next.js 16. This affects all three example apps that use eslint-config-next.
Additional Locations (2)
Bumps [next](https://github.com/vercel/next.js) from 15.3.6 to 16.1.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@v15.3.6...v16.1.6) --- updated-dependencies: - dependency-name: next dependency-version: 16.1.6 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/next-16.1.6
branch
from
fc352f4 to
5323743
Compare
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.
| "eslint-plugin-react-refresh": "^0.4.14", | ||
| "jsdom": "^27.1.0", | ||
| "next": "15.3.6", | ||
| "next": "16.1.6", |
There was a problem hiding this comment.
Next and eslint-config-next major mismatch
Medium Severity
next was bumped to 16.1.6 while eslint-config-next (and the lockfile’s @next/eslint-plugin-next) remains on 15.4.6, which can create peer-dependency/version skew and cause next lint (or installs with strict peer deps) to fail or behave inconsistently across environments.
Bumps next from 15.3.6 to 16.1.6.
Release notes
Sourced from next's releases.
... (truncated)
Commits
adf8c61v16.1.6098c0c0[backport][ci] Make gh auth status optional when triggering a release (#89100)a43df32Backport/docs fixes jan 25 16.1.x (#89124)d6d5734tweak LRU sentinel cache key (#89123)4324698backport: implement LRU cache with invocation ID scoping for minimal mode res...23c4649[backport] Upgrade to swc 54 (#88207) (#89103)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)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)