Repository navigation
chore(deps): bump next from 16.3.8 to 16.4.1 in /apps/apollo-docs - #1455
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [next](https://github.com/vercel/next.js) from 16.3.8 to 16.4.1. - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](vercel/next.js@v16.3.8...v16.4.1) --- updated-dependencies: - dependency-name: next dependency-version: 16.4.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Storybook visual diff⏭️ Skipped: the apollo-design preview deployment did not succeed, so no comparison ran. Logs Updated (PT): Oct 22, 2026, 01:10:27 PM |
📊 Coverage + size by packagePer-package bundle size on this PR (no JS/TS source changes detected under
"Coverage" is each package's own |
There was a problem hiding this comment.
🟡 Changes recommended
The stale lockfile blocks frozen installs, and differing Next.js pins across workspaces fail dependency-consistency checks.
2 open issues
What changed in this PR
Updates the Apollo documentation app’s Next.js dependency from 16.3.8 to 16.4.1 to adopt the security fixes described in the release notes.
Changes:
- Bumps the exact Next.js version in the app manifest.
- Leaves application code unchanged.
| File | Description |
|---|---|
apps/apollo-docs/package.json |
Updates the Next.js dependency to 16.4.1. |
Review effort: Balanced
| "@emotion/styled": "^11.14.1", | ||
| "@mui/material": "^5.18.0", | ||
| "next": "16.3.8", | ||
| "next": "16.4.1", |
| "@emotion/styled": "^11.14.1", | ||
| "@mui/material": "^5.18.0", | ||
| "next": "16.3.8", | ||
| "next": "16.4.1", |

Bumps next from 16.3.8 to 16.4.1.
Release notes
Sourced from next's releases.
... (truncated)
Commits
7217011v16.4.11798e42[cd] Allow branch to get published9571ec8[lts-active][next/image] Bumpsharp(#234)a4cea6a[lts-active][react] Improve Server Component transport protocol (#193)8df0d97[lts-active][test] Backport various deploy test fixes (#100114)ac9afcc[lts-active] Fix google tag manager e2e test, assume GTM 200s instead of 404i...e273d5bv16.4.0fdf41d6[ai-upgrade] discover upgrade models and reasoning efforts from agent CLIs (#...c3e76adv16.4.0-canary.6347c6cc8Document next analyze export in the package bundling guide (#99735)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.