Skip to content

Update nextjs monorepo to v16.1.6#328

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

Update nextjs monorepo to v16.1.6#328
renovate[bot] wants to merge 1 commit intomainfrom
renovate/nextjs-monorepo

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 20, 2026

This PR contains the following updates:

Package Change Age Confidence
eslint-config-next (source) 16.1.316.1.6 age confidence
next (source) 16.1.516.1.6 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

vercel/next.js (eslint-config-next)

v16.1.6

Compare Source

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

Core Changes
  • Upgrade to swc 54 (#​88207)
  • implement LRU cache with invocation ID scoping for minimal mode response cache (#​88509)
  • tweak LRU sentinel key (#​89123)
Credits

Huge thanks to @​mischnic, @​wyattjoh, and @​ztanner for helping!

v16.1.5

Compare Source

Please refer the following changelogs for more information about this security release:

https://vercel.com/changelog/summaries-of-cve-2025-59471-and-cve-2025-59472
https://vercel.com/changelog/summary-of-cve-2026-23864

v16.1.4

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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.

@renovate renovate bot added the renovate label Jan 20, 2026
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch 2 times, most recently from a3ab69f to 17694fb Compare January 26, 2026 20:20
@renovate renovate bot changed the title Update nextjs monorepo to v16.1.4 Update nextjs monorepo to v16.1.5 Jan 26, 2026
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from 17694fb to f8b2546 Compare January 27, 2026 21:09
@renovate renovate bot changed the title Update nextjs monorepo to v16.1.5 Update dependency eslint-config-next to v16.1.5 Jan 27, 2026
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from f8b2546 to 91b7589 Compare January 28, 2026 01:00
@renovate renovate bot changed the title Update dependency eslint-config-next to v16.1.5 Update nextjs monorepo to v16.1.6 Jan 28, 2026
@renovate renovate bot changed the title Update nextjs monorepo to v16.1.6 Update dependency eslint-config-next to v16.1.6 Jan 28, 2026
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch 2 times, most recently from 0536235 to 1a33652 Compare January 28, 2026 22:05
@renovate renovate bot changed the title Update dependency eslint-config-next to v16.1.6 Update nextjs monorepo to v16.1.6 Jan 28, 2026
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from 1a33652 to 59f32fe Compare February 4, 2026 10:59
@renovate renovate bot changed the title Update nextjs monorepo to v16.1.6 Update dependency eslint-config-next to v16.1.6 Feb 4, 2026
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch 3 times, most recently from cf9d48c to aa3f783 Compare February 4, 2026 12:09
@renovate renovate bot changed the title Update dependency eslint-config-next to v16.1.6 Update nextjs monorepo to v16.1.6 Feb 4, 2026
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch 3 times, most recently from 119900c to c88ab38 Compare February 6, 2026 10:14
@renovate renovate bot force-pushed the renovate/nextjs-monorepo branch from c88ab38 to facb6e4 Compare February 12, 2026 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants