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

• e893fb2: Bump patch supported range to 16.1.2

Summary by CodeRabbit

Release Notes

• Chores
  • Released version 2.1.14 with an updated patch supported range to 16.1.2.

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

[coderabbitai]

Walkthrough

A patch release (v2.1.14) of the next-ws package with updated Next.js supported patch range to 16.1.2. The release entry is formally documented in the changelog, and the changeset file is removed as part of the release process.

Changes

Cohort / File(s)	Summary
Release metadata package.json, CHANGELOG.md, .changeset/V6CUYgqg3Xi42.md	Version bumped from 2.1.13 to 2.1.14; new changelog entry added documenting the patch range update to 16.1.2; changeset entry removed post-release

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Bump patch supported range to 16.1.2 #165: Directly inverse operation—adds the changeset entry and updates the Next.js patch-supported range to 16.1.2 that this PR removes and documents.
• Pending Releases #158: Modifies the same release metadata files (changeset, CHANGELOG, package.json) to manage patch-release entries and supported version ranges.
• Bump patch supported range to 16.0.8 #152: Updates the patch-supported Next.js version ranges in repository metadata, addressing the same version-range management concern.

Suggested labels

patches

Poem

🐰 A patch hops in, version now 2.1.14,
Next.js sixteen-point-one-point-two's here to stay,
Changelog updated, changeset put away,
Release notes tidied, all neat and tidy today! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title "Pending Releases" is generic and vague, failing to convey meaningful information about the specific package version bump or changeset being released.	Consider using a more descriptive title such as "Release [email protected]" or "Bump next-ws patch version to 2.1.14" to clearly communicate the main change.

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

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

---

---

📜 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 e893fb2 and 0739dbf.

📒 Files selected for processing (3)

• .changeset/V6CUYgqg3Xi42.md
• CHANGELOG.md
• package.json

💤 Files with no reviewable changes (1)

• .changeset/V6CUYgqg3Xi42.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 looks correct.

The patch version increment from 2.1.13 to 2.1.14 is appropriate and consistent with the changelog entry.

CHANGELOG.md (1)

3-7: Changelog entry is properly formatted and follows the established pattern.

The entry correctly uses the project's standard format with @changesets/changelog-git. However, the "patch supported range" value (16.1.2) does not refer to a Next.js version. Next.js does not have a 16.1.2 release—it currently uses 15.x versions. The "patch supported range" appears to be an internal version identifier for this library. No verification against a non-existent Next.js version is needed.

Likely an incorrect or invalid review comment.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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