Release/2.6.3

[ttypic]

• Fixed useChannel hook can throw exception in the effect if connection is closed #1938

Summary by CodeRabbit

• Bug Fixes

  • Fixed an issue with the useChannel hook that could throw an exception when the connection is closed (Issue useChannel hook can throw exception in the effect if connection is closed #1938)
  • Resolved an issue with FetchRequest to respect the disableConnectivityCheck client option (Issue Fix web FetchRequest does not respect disableConnectivityCheck client option #1925)
  • Corrected typings related to RealtimeChannel.modes (Issue Fix typings for RealtimeChannel.modes #1955)

• Chores

  • Updated package version to 2.6.3

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request introduces version 2.6.3 of the Ably JavaScript library, focusing on addressing issues with the useChannel hook in React. The changes include updating the version number across multiple files (CHANGELOG.md, package.json, and AblyReactHooks.ts) and preparing for handling exceptions when the connection is closed during channel interactions. Additionally, the FetchRequest now respects the disableConnectivityCheck client option.

Changes

File	Change Summary
CHANGELOG.md	Added version 2.6.3 entry describing fixes for useChannel hook, FetchRequest, and RealtimeChannel.modes
package.json	Updated version from 2.6.2 to 2.6.3
src/platform/react-hooks/src/AblyReactHooks.ts	Updated version constant from '2.6.2' to '2.6.3'

Assessment against linked issues

Objective	Addressed	Explanation
Handle exception when connection is closed in useChannel hook [#1938]	✅
Respect disableConnectivityCheck option in FetchRequest [#1925]	✅

Possibly related PRs

• [ECO-5184] feat: update channel hooks implementation #1947: The changes in the main PR regarding the useChannel hook and the attachOnSubscribe property are directly related to the modifications made in PR [ECO-5184] feat: update channel hooks implementation #1947, which also addresses the handling of channel attachment and introduces the attachOnSubscribe flag to improve reliability.

Suggested reviewers

• AndyTWF

Poem

🐰 A rabbit's tale of version might,
Code hopping to version two-point-six-three's light!
Hooks fixed with care, exceptions now tamed,
In Ably's realm, another milestone claimed! 🚀

---

📜 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 2425691 and 59da423.

📒 Files selected for processing (1)

• CHANGELOG.md (1 hunks)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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.

[VeskeR]

Evgeny is on holiday and a couple more PRs got merged into the main while this relase PR was opened. I updated the changelog to include the fix for #1955