Release 2.10.1

[VeskeR]

Summary by CodeRabbit

• Bug Fixes

  • Resolved a minimization issue affecting Next.js 15.4+ canary builds.

• Chores

  • Updated version to 2.10.1 in documentation and package metadata.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This update increments the package version from 2.10.0 to 2.10.1, documents the new patch release in the changelog, and updates the exported version constant. The release addresses a minimization issue for Next.js 15.4+ canary builds, with no other changes to code, dependencies, or public APIs.

Changes

File(s)	Change Summary
CHANGELOG.md	Added entry for patch release 2.10.1, noting a fix for Next.js 15.4+.
package.json	Updated version from 2.10.0 to 2.10.1.
src/platform/react-hooks/src/AblyReactHooks.ts	Updated exported version constant to '2.10.1'.

Possibly related PRs

• Chore: Release version 2.6.2 #1946: Updates both the package version and the exported version constant in the same file, similar to this PR.
• Release 2.10.0 #2050: Sequential version bump updating package version and exported version constant without other code changes.

Suggested reviewers

• ttypic

Poem

A patch hops in, so small and neat,
To fix a bug and not repeat.
The version bumps, the changelog grows,
A tiny change, as rabbit knows.
Next.js canaries now at peace—
With 2.10.1, all worries cease!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 14891a1 and 5b65d4b.

📒 Files selected for processing (1)

• CHANGELOG.md (1 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release/2.10.1

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/platform/react-hooks/src/AblyReactHooks.ts (1)

15-15: Centralize version source to avoid manual drift

version is now hard-coded here and in package.json. Two separate declarations are easy to get out-of-sync on the next bump.
Consider injecting the package version at build time (e.g. via rollup-plugin-replace, webpack DefinePlugin, or simply reading from package.json in a small build-step) so there’s a single source of truth.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 61e8fc6 and 14891a1.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (3)

• CHANGELOG.md (1 hunks)
• package.json (1 hunks)
• src/platform/react-hooks/src/AblyReactHooks.ts (1 hunks)

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

• GitHub Check: test-npm-package
• GitHub Check: test-node (16.x)
• GitHub Check: test-node (18.x)
• GitHub Check: test-node (20.x)
• GitHub Check: test-browser (chromium)
• GitHub Check: test-browser (firefox)
• GitHub Check: test-browser (webkit)

🔇 Additional comments (2)

package.json (1)

4-4: Remember to commit the lock-file

package.json’s version is updated, but the PR does not show a matching change to package-lock.json / npm-shrinkwrap.json.
If the repository tracks a lock-file, bump its "version" field as well to keep npm publish warnings away.

CHANGELOG.md (1)

5-8: Changelog entry looks good

Entry follows existing style and links resolve correctly.