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

• b6f2d43: Bump patch supported range to 16.1.6
• 569d1cd: Bump patch supported range to 16.1.5

Summary by CodeRabbit

• Chores
  • Package version bumped to 2.1.16 and released as a patch update
  • Expanded supported patch version ranges to include versions 16.1.5 and 16.1.6 to improve compatibility across different runtime environments
  • Updated release notes, package documentation, and version tracking information to reflect the new patch release
  • Cleaned up obsolete version management files

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

[coderabbitai]

Walkthrough

This PR removes a .changeset entry and updates release metadata: adds a new CHANGELOG.md entry for version 2.1.16 (recording patch bumps to Next.js 16.1.6 and 16.1.5) and updates package.json to version 2.1.16. No runtime code changes.

Changes

Cohort / File(s)	Summary
Release metadata .changeset/WFGppyIyMmqp4.md	Deleted changeset entry (consumed/removed patch release instruction)
Release documentation & version bump CHANGELOG.md, package.json	package.json version set to 2.1.16; CHANGELOG.md updated with 2.1.16 entry documenting patch bumps to Next.js 16.1.6 and 16.1.5

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Bump patch supported range to 16.1.5 #171: Adds/removes changeset entry related to bumping supported patch range to 16.1.5.
• Bump patch supported range to 16.1.4 #169: Adjusts release metadata for next-ws patch support ranges (related patch-range edits).
• Pending Releases #170: Modifies release metadata and changeset entries around next-ws patch bumps (closely related).

Suggested labels

dependencies, patches

Poem

🐇 I nibbled a changeset, then hopped away light,
Version 2.1.16 gleams in the night,
Changelog leaves rustle with 16.1.6 and 5,
No code was harmed — just metadata dives,
A little rabbit cheers this tidy release.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Pending Releases' is vague and does not clearly convey the specific change being made. It lacks specificity about what is being released or prepared.	Consider a more descriptive title such as 'Release [email protected]' or 'Bump next-ws to version 2.1.16' to clearly indicate the package and version being released.

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

---

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