Bump Next.js from 16.2.6 to 16.3.3 in /site - #3
Conversation
Bumps [next](https://github.com/vercel/next.js) from 16.2.6 to 16.2.11. - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](vercel/next.js@v16.2.6...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>
b2b4e84 to
ac75b0c
Compare
|
Cleanup recovery: the original manifest-only Next.js 16.2.11 update failed the frozen site install and was superseded by the current stable 16.3.3 security release, published with two critical unauthenticated RCE fixes. After Dependabot concurrently rebased the branch to ac75b0c, the recovery was replayed as descendant b8a64b6 without rewriting that work. The head aligns next and eslint-config-next at 16.3.3 and commits the Bun 1.3.14 lockfile. Local frozen install, site lint/build/runtime tests, full 73-test repository check, generated-tree reproducibility, and package inspection passed. CI run https://github.com/hraness/oh/actions/runs/33076249534 passed on synthetic merge 1b99990 from current main 24f5226 and the exact recovery head. The source branch remains retained. |
Bumps next from 16.2.6 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