Bump patch supported range to 16.1.0

[k0d13]

Bump patch supported range to 16.1.0

Summary by CodeRabbit

• Chores
  • Updated next-ws to support Next.js versions up to 16.1.0.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[changeset-bot]

🦋 Changeset detected

Latest commit: b2d54d4

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

Walkthrough

This PR updates the next-ws package to support Next.js version 16.1.0 by extending the compatible version range in the patch configuration from 16.0.10 to 16.1.0, and updates the workspace catalog version accordingly.

Changes

Cohort / File(s)	Change Summary
Changeset Release .changeset/t2bllqIBJWKnP.md	Adds changeset file marking a patch release for next-ws package with new supported version range 16.1.0
Workspace Configuration pnpm-workspace.yaml	Updates Next.js catalog version from 16.0.10 to 16.1.0
Patch Version Constraint src/patches/patch-2.ts	Updates version constraint upper bound from 16.0.10 to 16.1.0 (>=15.0.0 <=16.1.0)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5–10 minutes

• Straightforward, homogeneous version updates across three files with consistent change patterns
• No logic changes or complex interactions to review

Possibly related PRs

• Bump patch supported range to 16.0.10 #155: Updates patch gating and version constraints in the same files to extend Next.js support compatibility range
• Bump patch supported range to 16.0.8 #152: Directly modifies the patch-supported Next.js version constraint in src/patches/patch-2.ts
• Pending Releases #156: Prior changeset/release that established the previous upper version bound being superseded by this PR

Suggested labels

dependencies, patches

Poem

🐰 Hops of joy for versions new!
Next.js 16.1.0 joins the crew,
Patches tuned and ranges extended,
Compatibility perfectly blended! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: bumping the patch supported range to 16.1.0, which is confirmed across the changeset, workspace configuration, and patch file updates.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/bump-nextjs-16.1.0

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between afd5e79 and b2d54d4.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (3)

• .changeset/t2bllqIBJWKnP.md (1 hunks)
• pnpm-workspace.yaml (1 hunks)
• src/patches/patch-2.ts (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Testing

🔇 Additional comments (3)

.changeset/t2bllqIBJWKnP.md (1)

1-5: LGTM!

The changeset format is correct and the message clearly describes the version bump. This will properly document the patch release.

src/patches/patch-2.ts (1)

24-24: Ensure patch logic remains unchanged with Next.js 16.1.0 upgrade.

The version constraint update to support Next.js 16.1.0 is valid. Verify that the patched file paths (next:dist/server/request/headers.js and next:dist/server/request/cookies.js) remain compatible with 16.1.0 and confirm that patch steps have not been modified.

pnpm-workspace.yaml (1)

6-6: Next.js 16.1.0 is in canary stage; use stable 16.0.10 for production or await 16.1.0 stable release.

Next.js 16.1 was released on 18 December 2025, but it is only available as canary releases (e.g. 16.1.0-canary.19). Only stable releases are suitable for production. Next.js 16.0.10 LTS is the latest stable version and should be preferred unless your project requires canary features.

If upgrading to Next.js 16, verify Node.js 20.9.0 minimum requirement and that Node.js 18 is no longer supported. Next.js 16 introduces several breaking changes that developers must address during migration.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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