chore(deps): bump next from 16.2.9 to 16.2.11 in /frontend - #44
Closed
dependabot[bot] wants to merge 1 commit into
Closed
chore(deps): bump next from 16.2.9 to 16.2.11 in /frontend#44dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
Bumps [next](https://github.com/vercel/next.js) from 16.2.9 to 16.2.11. - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](vercel/next.js@v16.2.9...v16.2.11) --- updated-dependencies: - dependency-name: next dependency-version: 16.2.11 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/frontend/next-16.2.11
branch
from
July 26, 2026 18:41
4ce74f7 to
a4636a3
Compare
timothybrown
added a commit
that referenced
this pull request
Jul 26, 2026
….7.26.2 Closes the second advisory wave that surfaced after v2026.7.26.1: - next 16.2.9 -> 16.2.11 (batch of 18 Next.js advisories, 8 high / 10 medium, runtime). Supersedes Dependabot PR #44. - js-yaml override 4.2.0 -> 4.3.0 (dev; advisory < 4.3.0) - postcss override 8.5.15 -> 8.5.18 (build; advisory <= 8.5.17) js-yaml and postcss are transitive deps pinned via pnpm.overrides, so Dependabot's own security-update jobs for them fail with security_update_not_possible — they can only be resolved by bumping the overrides here. next 16.2.11 shipped 2026-07-21 (5 days ago), inside the 7-day minimum-release-age in .npmrc. Cooldown was bypassed for this one lockfile regen only (npm_config_minimum_release_age=0); the committed .npmrc stays at 10080 and the lockfile churn is scoped strictly to next/js-yaml/postcss. Verified: tsc clean, next build clean, 555 frontend tests pass. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QHDmg41wKKcwPreaoQyiGM
Contributor
Author
|
Looks like next is up-to-date now, so this is no longer needed. |
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.2.9 to 16.2.11.
Release notes
Sourced from next's releases.
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