Repository navigation
chore(deps): bump next from 16.3.7 to 16.4.0 - #493
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF ScorecardScorecard details
Scanned Files
|
Bumps [next](https://github.com/vercel/next.js) from 16.3.7 to 16.4.0. - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](vercel/next.js@v16.3.7...v16.4.0) --- updated-dependencies: - dependency-name: next dependency-version: 16.4.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/dev/next-16.4.0
branch
from
October 15, 2026 14:01
b709094 to
cbbdb5b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps next from 16.3.7 to 16.4.0.
Release notes
Sourced from next's releases.
... (truncated)
Commits
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)5b10604Revert stabilization offorbidden()andunauthorized()(#99734)f3a6f97Preserve configured output directories during static export (#99507)b22e5a2Rename skill to next-bundle-optimizer and document its usage (#99731)74dc549[turbo-tasks-backend] Clean up task state before publishing execution complet...ccf8c15v16.4.0-canary.62b8c7c7fImprove static route error guidance (#99724)Note
Medium Risk
Minor framework upgrade touches all Next apps and can change build, routing, caching, or Turbopack behavior without any code changes in this PR; smoke-test builds and critical flows after merge.
Overview
Bumps Next.js from
16.3.7to16.4.0across the monorepo root,sites/mainweb,sites/hacklytics2027, andtooling/tailwind, withpnpm-lock.yamlrefreshed so workspace packages (@trpc/next,next-auth,geist, etc.) resolve against the new version.The lockfile also picks up transitive updates bundled with Next 16.4.0 (e.g.
@next/env/ platform@next/swc-*binaries,sharp0.35.5, newercaniuse-lite). No application or config source changes—only dependency pins and the lockfile.@next/eslint-plugin-nextand@next/bundle-analyzerremain on 16.3.7 where they were already declared.Reviewed by Cursor Bugbot for commit cbbdb5b. Bugbot is set up for automated code reviews on this repo. Configure here.