Repository navigation
chore(deps): bump next from 16.3.6 to 16.3.8 - #27
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [next](https://github.com/vercel/next.js) from 16.3.6 to 16.3.8. - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](vercel/next.js@v16.3.6...v16.3.8) --- updated-dependencies: - dependency-name: next dependency-version: 16.3.8 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
Bot
added
dependencies
![justalab-agents[bot]](https://avatars.githubusercontent.com/u/159771991?s=60&v=4){kind=small}
There was a problem hiding this comment.
This PR bumps the next package from version 16.3.6 to 16.3.8, along with the corresponding lockfile updates for all related Next.js SWC binaries and a few transitive dependency upgrades (e.g., caniuse-lite, baseline-browser-mapping, nanoid, postcss). The change is a straightforward patch-level upgrade with no application code modifications. Note that eslint-config-next remains pinned at 16.3.6 in devDependencies, creating a minor version mismatch with the upgraded next package.
Findings outside the diff
These sit on lines this PR did not change, but this PR is what makes them wrong. They cannot be posted as inline comments.
-
[WARNING]
package.json:37—eslint-config-nextis pinned at16.3.6whilenexthas been bumped to16.3.8. These companion packages are typically kept at the same version. A mismatch can cause subtle lint rule inconsistencies or peer-dependency warnings, and becomes harder to track over time as the gap widens.Suggested fix:
Update `devDependencies` to `"eslint-config-next": "16.3.8"` to keep it aligned with the `next` version.
Reviewer callouts (1)
Non-blocking observations. Nothing here needs to change before merge.
.github:1— "The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see actions/runner-images#14748"
Bumps next from 16.3.6 to 16.3.8.
Release notes
Sourced from next's releases.
Commits
b0fad0dv16.3.8719e4c6[lts-active] Scope response cache keys to their source route (#218)e92db45[lts-active] Fix metadata propagation for deduplicated nested caches (#223)40c2ba9[lts-active] Match Next data paths case-sensitively (#196)2d9f50a[lts-active] Fix MCP middleware DNS rebinding (#213)bd9214f[lts-active] Fix draft mode leaks through cross-request'use cache'dedupli...8db4a62[lts-active][webpack] EnsuredynamicParamsis respected in `opengraph-image...e002ad6[lts-active] fix(next/image): Pin DNS resolution when fetching external image...4c20699v16.3.72521aec[backport] turbo-tasks-backend: fix strongly consistent read hanging on a can...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)