Skip to content

Conversation

@k0d13
Copy link
Owner

@k0d13 k0d13 commented Jan 28, 2026

Bump patch supported range to 16.1.6

Summary by CodeRabbit

  • Chores
    • Updated next-ws to version 16.1.6 with corresponding configuration updates to ensure consistent versioning across the project.

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

@changeset-bot
Copy link

changeset-bot bot commented Jan 28, 2026

🦋 Changeset detected

Latest commit: 2cb0cc2

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

@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 28, 2026
@coderabbitai
Copy link

coderabbitai bot commented Jan 28, 2026

Walkthrough

This PR updates the supported patch version range for next-ws from 16.1.4 to 16.1.6 across configuration and patch definition files, including a new changeset entry for the patch release.

Changes

Cohort / File(s) Summary
Version Bump
.changeset/TcEGDcnStJqvd.md, pnpm-workspace.yaml, src/patches/patch-2.ts
Increment next-ws patch support upper bound from 16.1.4 to 16.1.6 across workspace catalog, changeset metadata, and patch version constraint

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Poem

🐰 From sixteen dot one dot four, we hop once more,
To six the version climbs with glee,
A patch update so light and clean,
The smallest change you've ever seen,
Workspace and patches align in harmony! 🚀

🚥 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 'Bump patch supported range to 16.1.6' directly and clearly summarizes the main change across all modified files—updating version constraints and changeset entries.
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.

@k0d13
Copy link
Owner Author

k0d13 commented Jan 28, 2026

This will be reopened at some point without conflicts

@k0d13 k0d13 closed this Jan 28, 2026
@k0d13 k0d13 deleted the chore/bump-nextjs-16.1.6 branch January 28, 2026 01:02
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