Skip to content

chore(deps): update nextjs monorepo to v16.3.2 - #885

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/nextjs-monorepo
Open

chore(deps): update nextjs monorepo to v16.3.2#885
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/nextjs-monorepo

Conversation

@renovate

@renovate renovate Bot commented May 7, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@next/eslint-plugin-next (source) 16.2.516.3.2 age confidence
eslint-config-next (source) 16.2.516.3.2 age confidence

Release Notes

vercel/next.js (@​next/eslint-plugin-next)

v16.3.2

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes
  • [backport] Scope app-entry export validation to files inside the app directory (#​97357)
  • [backport] Fix catch-all index page being served for every other slug (#​97416)
  • [16.3] Turbopack: don't trace embedded WASM loader helpers (#​97353) (#​97463)
  • [16.3] Turbopack: retain conditions when replacing resolve request keys (#​97453)
  • [16.3.x] Fix Turbopack worker chunk loading with asset prefix (#​97419)
  • [16.3.x] Authenticate Turborepo remote caching with OIDC instead of a static PAT (#​97603)
Credits

Huge thanks to @​lubieowoce, @​unstubbable, @​timneutkens, @​mischnic, and @​eps1lon for helping!

v16.3.1

Compare Source

What's Changed

Full Changelog: vercel/next.js@v16.3.0...v16.3.1

v16.3.0

Compare Source

v16.2.12

Compare Source

v16.2.11

Compare Source

This release contains security fixes for the following advisories:

High:

Moderate:

v16.2.10

Compare Source

Contains no changes except publishing @next/swc-wasm-web which was accidentally not published since 16.2.4.

v16.2.9

Compare Source

Empty release to ensure next@latest points at a stable release. Next.js only allows publishing with Trusted Publishing enabled. In order to fix NPM dist-tags, we have to release a new version. Updating dist-tags is not possible with Trusted Publishing.

v16.2.8

Compare Source

Release with no changes in an attempt to fix next@latest pointing at a prerelease version.

v16.2.7

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes
  • Backport documentation fixes for v16.2 (#​93804)
  • [backport] Patch playwright-core to resolve _finishedPromise on requestFailed (#​93920)
  • [backport] Fix dev mode hydration failure when page is served from HTTP cache (#​93492)
  • [backport] Fix catch-all router.query corruption with basePath + rewrites (#​93917)
  • [backport] Encode non-ASCII characters in cache tags at construction (#​93918)
  • [backport] Fix server action forwarding loop with middleware rewrites (#​93919)
  • [backport] Turbopack: switch from base40 to base38 hash encoding (#​93932)
  • [ci] Disable hanging node 24 typescript tests on 16.2 backport branch (#​94164)
  • [backport] Fix "type: module" in project dir when using standalone or adapters (#​94050)
  • [backport] Propagate adapter preferred regions (#​94200)
  • [16.2.x] Don't drop FormData entries (#​94240)
  • [backport] feat(turbopack): add LocalPathOrProjectPath PostCSS config resolution (#​94284)
Credits

Huge thanks to @​eps1lon, @​icyJoseph, @​unstubbable, @​mischnic, @​bgw, @​timneutkens, and @​lukesandberg for helping!

v16.2.6

Compare Source

[!NOTE]
This release contains security fixes and backported bug fixes. It does not include all pending features/changes on canary.

Security Fixes

The following advisories have been addressed:

High:

Moderate:

Low:

Core Changes
  • fix: preserve HTTP access fallbacks during prerender recovery (#​92231)
  • Fix fallback route params case in app-page handler (#​91737)
  • Fix invalid HTML response for route-level RSC requests in deployment adapter (#​91541)
  • Patch setHeader for direct route handlers (#​93101)
  • Include deployment id in cacheHandlers keys (#​93453)
  • Fix double-encoding of URL pathname parts in client param parsing (#​93491)

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@vercel

vercel Bot commented May 7, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
breval Ready Ready Preview Aug 21, 2026 12:04pm

@renovate
renovate Bot force-pushed the renovate/nextjs-monorepo branch from f864762 to e779ac7 Compare May 13, 2026 09:26
@renovate renovate Bot changed the title fix(deps): update nextjs monorepo chore(deps): update nextjs monorepo to v16.2.6 May 13, 2026
@renovate
renovate Bot force-pushed the renovate/nextjs-monorepo branch from e779ac7 to 05bbfb6 Compare June 2, 2026 01:52
@renovate renovate Bot changed the title chore(deps): update nextjs monorepo to v16.2.6 chore(deps): update nextjs monorepo to v16.2.7 Jun 2, 2026
@renovate
renovate Bot force-pushed the renovate/nextjs-monorepo branch from 05bbfb6 to 605e323 Compare June 10, 2026 00:32
@renovate renovate Bot changed the title chore(deps): update nextjs monorepo to v16.2.7 chore(deps): update nextjs monorepo to v16.2.9 Jun 10, 2026
@renovate
renovate Bot force-pushed the renovate/nextjs-monorepo branch from 605e323 to 2c6383d Compare June 13, 2026 15:44
@renovate
renovate Bot force-pushed the renovate/nextjs-monorepo branch from 2c6383d to d68a59c Compare June 29, 2026 08:39
@renovate
renovate Bot force-pushed the renovate/nextjs-monorepo branch from d68a59c to 320cf8e Compare July 1, 2026 21:34
@renovate renovate Bot changed the title chore(deps): update nextjs monorepo to v16.2.9 chore(deps): update nextjs monorepo to v16.2.10 Jul 1, 2026
@renovate
renovate Bot force-pushed the renovate/nextjs-monorepo branch from 320cf8e to e6db64e Compare July 21, 2026 00:35
@renovate
renovate Bot force-pushed the renovate/nextjs-monorepo branch from e6db64e to c7fedef Compare July 21, 2026 16:09
@renovate renovate Bot changed the title chore(deps): update nextjs monorepo to v16.2.10 chore(deps): update nextjs monorepo to v16.2.11 Jul 21, 2026
@renovate
renovate Bot force-pushed the renovate/nextjs-monorepo branch from c7fedef to b63b396 Compare July 26, 2026 05:07
@renovate renovate Bot changed the title chore(deps): update nextjs monorepo to v16.2.11 chore(deps): update nextjs monorepo to v16.2.12 Jul 26, 2026
@renovate
renovate Bot force-pushed the renovate/nextjs-monorepo branch from b63b396 to d3453a6 Compare August 3, 2026 21:38
@renovate renovate Bot changed the title chore(deps): update nextjs monorepo to v16.2.12 chore(deps): update nextjs monorepo to v16.3.0 Aug 3, 2026
@renovate
renovate Bot force-pushed the renovate/nextjs-monorepo branch from d3453a6 to 4b090fb Compare August 13, 2026 23:11
@renovate renovate Bot changed the title chore(deps): update nextjs monorepo to v16.3.0 chore(deps): update nextjs monorepo to v16.3.1 Aug 13, 2026
@renovate
renovate Bot force-pushed the renovate/nextjs-monorepo branch from 4b090fb to 2ff79c8 Compare August 21, 2026 12:03
@renovate renovate Bot changed the title chore(deps): update nextjs monorepo to v16.3.1 chore(deps): update nextjs monorepo to v16.3.2 Aug 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants