chore(deps): bump next from 15.5.19 to 16.2.11 in /compliance-firewall-agent#235
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Bumps [next](https://github.com/vercel/next.js) from 15.5.19 to 16.2.11. - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](vercel/next.js@v15.5.19...v16.2.11) --- updated-dependencies: - dependency-name: next dependency-version: 16.2.11 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/compliance-firewall-agent/next-16.2.11
branch
from
July 22, 2026 03:46
1d7b80f to
1efc0ef
Compare
2 tasks
thecelestialmismatch
added a commit
that referenced
this pull request
Jul 22, 2026
* chore(deps): bump next + eslint-config-next to 16.2.11 * chore(config): migrate to ESLint CLI + Next 16 config Next 16 removed `next lint` and the `eslint` config key, and defaults builds to Turbopack. - Replace `.eslintrc.json` with flat `eslint.config.mjs` (next/core-web-vitals + typescript + unused-imports). Scope ignores restore the `next lint` surface (legacy/, sdk/, data dirs were never linted). react-hooks v7's new rules (set-state-in-effect, purity, refs, …) are set to warn — they fire on unchanged code that passed under Next 15; keeping the Next-15 lint outcome (green) instead of a 39-file refactor. Lint: 0 errors. - next.config.js: drop the removed `eslint` key (lint is its own CI step now). - build → `next build --webpack`: Sentry's withSentryConfig injects a webpack config in prod (DSN set), which Turbopack-by-default rejects. Pin webpack so the prod build matches today's known-good behavior. Turbopack adoption is separate. - tsconfig.json: Next 16's auto-managed patch (react-jsx, .next/dev/types). Verified: tsc 0, lint 0 errors, 1471 tests, build 0. Browser-smoked the prod build (next start): homepage + /demo render clean, 0 console errors, and the full scan → NIST-mapped findings (name-only) → PDF/$499 CTA money path works.
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/compliance-firewall-agent/next-16.2.11
branch
July 22, 2026 04:16
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 15.5.19 to 16.2.11.
Release notes
Sourced from next's releases.
... (truncated)
Commits
9beca08v16.2.113c48c7a[16.x] Fix Turbopack middleware matcher with i18n single localeac1eff3[16.x] Improve performance of checking valid MPA form submissions9a4651e[16.x] EnforceserverActions.bodySizeLimitfor Server Actions in Edge runtimeb512063[16.x] Set correct origin for internal redirects in custom serverd303326[16.x] Ensure exotic rewrite param values are properly encoded73b9487[16.x] fix(fetch-cache): key fetch(Request, init) by the effective requestbf9d17f[16.x] fix(incremental-cache): byte-exact fetch cache key for binary bodiesfe28768[16.x] fix(next/image): improve performance of detectContentType()d8afb8d[16.x] Performance improvements when decoding React Server function payloads