Skip to content

Conversation

@k0d13
Copy link
Owner

@k0d13 k0d13 commented Jan 20, 2026

Bump patch supported range to 16.1.4

Summary by CodeRabbit

Chores

  • Released patch version 16.1.4
  • Extended Next.js compatibility to version 16.1.4

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

@changeset-bot
Copy link

changeset-bot bot commented Jan 20, 2026

🦋 Changeset detected

Latest commit: a8e3256

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
Copy link

coderabbitai bot commented Jan 20, 2026

Walkthrough

This PR establishes a patch release for the next-ws package, updating the supported version from 16.1.3 to 16.1.4. A changeset entry is added, and version constraints are updated in the workspace configuration and patch declaration file.

Changes

Cohort / File(s) Summary
Release Metadata
\.changeset/bxzaEvoVljUTZ\.md
New changeset entry added for next-ws patch release (16.1.4) with front-matter configuration
Version Configuration
pnpm-workspace\.yaml
Catalogue version bumped from 16.1.3 to 16.1.4
Patch Scope
src/patches/patch-2\.ts
Upper bound of Next.js version range extended from <=16.1.3 to <=16.1.4 in patch declaration

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

Suggested labels

dependencies, patches

Poem

🐰 A version bump, so small yet grand,
From 16.1.3 to 4 we stand,
The changeset speaks, the patches align,
Another release of next-ws fine! ✨

🚥 Pre-merge checks | ✅ 3
✅ 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 clearly summarises the main change: bumping the supported Next.js version range to 16.1.4 across the patch declaration, changeset, and workspace configuration.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing touches
  • 📝 Generate docstrings

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

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

@github-actions github-actions bot added dependencies Updates or changes related to project dependencies patches Updates or fixes related to Next.js patches labels Jan 20, 2026
@k0d13 k0d13 merged commit 170d191 into main Jan 20, 2026
9 checks passed
@k0d13 k0d13 deleted the chore/bump-nextjs-16.1.4 branch January 20, 2026 02:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Updates or changes related to project dependencies patches Updates or fixes related to Next.js patches

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants