Pending Releases

[k0d13]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

Patch Changes

• 9bffbf4: Bump patch supported range to 16.1.1

Summary by CodeRabbit

• Chores
  • Bumped package version to 2.1.12
  • Updated changelog

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

[coderabbitai]

Walkthrough

This PR removes a changeset entry and releases version 2.1.12 of the next-ws package with a single patch update bumping the supported patch range to 16.1.1, reflected in updated CHANGELOG.md and package.json version fields.

Changes

Cohort / File(s)	Summary
Release Patch .changeset/1pGCCp4Ovpnq5.md, CHANGELOG.md, package.json	Removed changeset entry; added v2.1.12 changelog entry documenting patch for supported range bump; incremented package version from 2.1.11 to 2.1.12

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Bump patch supported range to 16.1.1 #159: Reverses the changeset entry and release metadata for the same patch supported range bump.
• Pending Releases #153: Removes auto-generated changeset release entries and associated CHANGELOG/package.json bumps for different patch versions.
• Bump patch supported range to 16.0.8 #152: Modifies Next.js patch-support metadata and changeset entries for the next-ws package.

Suggested labels

patches

Poem

🐰 A tiny hop from one-one to one-two,
The patch notes say what we must do,
Version bumps like carrots grow,
Changelog records steal the show!
Hop along, the release is through! 🥕

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Pending Releases' is vague and generic, using non-descriptive terminology that doesn't convey meaningful information about the specific package version bump or changeset.	Consider using a more specific title such as 'Release [email protected]' or 'Release: Bump patch supported range to 16.1.1' to clearly indicate the package being released and the version number.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch changeset-release/main

---

📜 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 9bffbf4 and bfd3e8c.

📒 Files selected for processing (3)

• .changeset/1pGCCp4Ovpnq5.md
• CHANGELOG.md
• package.json

💤 Files with no reviewable changes (1)

• .changeset/1pGCCp4Ovpnq5.md

⏰ 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 (2)

package.json (1)

3-3: Version bump is consistent with release objectives.

The patch version has been correctly incremented from 2.1.11 to 2.1.12 to reflect the Next.js patch-supported range update to 16.1.1. No dependencies, exports, or other package metadata have been altered.

CHANGELOG.md (1)

3-8: Changelog entry is properly formatted and correctly positioned.

The new 2.1.12 section follows the established changelog conventions: version header, "Patch Changes" subsection, and commit reference with descriptive message. The entry is correctly placed before version 2.1.11, maintaining chronological order.

---

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.}