8000 Update all of nextjs 16.1.0 → 16.1.4 (patch) by depfu[bot] · Pull Request #19604 · tailwindlabs/tailwindcss · GitHub
[go: up one dir, main page]

Skip to content

Conversation

@depfu
Copy link
Contributor
@depfu depfu bot commented Jan 27, 2026

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ eslint-config-next (16.1.0 → 16.1.4)

Sorry, we couldn't find anything useful about this release.

✳️ next (16.1.0 → 16.1.4) · Repo

Release Notes

16.1.4

Note

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

Core Changes

  • Only filter next config if experimental flag is enabled (#88733)

Credits

Huge thanks to @mischnic for helping!

16.1.3

Note

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

Core Changes

  • Fix linked list bug in LRU deleteFromLru (#88652)
  • Fix relative same host redirects in node middleware (#88253)

Credits

Huge thanks to @acdlite and @ijjk for helping!

16.1.2

Note

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

Core Changes

  • Turbopack: Update to swc_core v50.2.3 (#87841) (#88296)
    • Fixes a crash when processing mdx files with multibyte characters. (#87713)
  • Turbopack: mimalloc upgrade and enabling it on musl (#88503) (#87815) (#88426)
    • Fixes a significant performance issue on musl-based Linux distributions (e.g. Alpine in Docker) related to musl's allocator.
    • Other platforms have always used mimalloc, but we previously did not use mimalloc on musl because of compilation issues that have since been resolved.

Credits

Huge thanks to @mischnic for helping!

16.1.1

Note

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

Core Changes

  • Turbopack: Create junction points instead of symlinks on Windows (#87606)

Credits

Huge thanks to @sokra and @ztanner for helping!

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 12 commits:


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot requested a review from a team as a code owner January 27, 2026 20:25
@depfu depfu bot added the depfu label Jan 27, 2026
@coderabbitai
Copy link
coderabbitai bot commented Jan 27, 2026

Walkthrough

This pull request updates dependency versions across two Next.js playground projects. The next package is bumped from version ^16.1.0 to ^16.1.4 in both the main and v3 playground directories. Additionally, the eslint-config-next package receives the same version increment from ^16.1.0 to ^16.1.4 in both locations. These are patch-level version updates within the same minor version range. No structural changes, script modifications, or other dependencies are affected by these updates.

🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The PR title clearly and concisely summarizes the main change: updating Next.js from 16.1.0 to 16.1.4 across the playground packages.
Description check ✅ Passed The PR description is directly related to the changeset, providing detailed release notes for the Next.js version update and explaining the bug fixes included in the patch versions.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Comment @coderabbitai help to get the list of available commands and usage tips.

@depfu
Copy link
Contributor Author
depfu bot commented Jan 28, 2026

Closed in favor of #19609.

@depfu depfu bot closed this Jan 28, 2026
@depfu depfu bot deleted the depfu/update/pnpm/group/nextjs-16.1.4 branch January 28, 2026 16:21
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

0