Release 2.9.0 - LiveObjects

[VeskeR]

release for LiveObjects feature #2007

Summary by CodeRabbit

• Documentation

  • Updated changelog to announce version 2.9.0, highlighting the introduction of Ably LiveObjects for realtime state synchronization across users and devices. Includes a link to official documentation.

• Chores

  • Bumped package version to 2.9.0.
  • Updated version constant to reflect the new release.

[coderabbitai]

Walkthrough

The changes update the project to version 2.9.0, as reflected in the changelog, package metadata, and a version constant in the React hooks source. The changelog documents the addition of Ably LiveObjects, a new feature for realtime state synchronization, and provides a link to further documentation.

Changes

File(s)	Change Summary
CHANGELOG.md	Added entry for version 2.9.0, describing the new Ably LiveObjects feature and linking docs.
package.json	Updated package version from 2.8.0 to 2.9.0.
src/platform/react-hooks/src/AblyReactHooks.ts	Updated exported constant version from '2.8.0' to '2.9.0'.

Poem

A hop, a skip, we reach two-nine,
LiveObjects now in perfect line.
States that sync and updates fly,
Across the clouds, our data’s nigh.
With versions bumped and docs anew,
This rabbit cheers the work you do!
🐇✨

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

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

[mschristensen]

Approving ahead of #2007, looks good once merged

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 37b5815 and 77027fc.

⛔ 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 (7)

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

🔇 Additional comments (2)

package.json (1)

4-4:

Details

✅ Verification successful

Confirm Lockfile Update.

The version field was bumped to 2.9.0. Please ensure that the lockfile (package-lock.json or yarn.lock) has been regenerated and committed to reflect this new version.

---

🏁 Script executed:

#!/bin/bash
# Verify lockfile contains the updated version
if grep -R '"version": "2.9.0"' package-lock.json; then
  echo "package-lock.json updated"
else
  echo "ERROR: package-lock.json does not contain version 2.9.0"
  exit 1
fi

if [ -f yarn.lock ]; then
  if grep -R 'version "2.9.0"' yarn.lock; then
    echo "yarn.lock updated"
  else
    echo "ERROR: yarn.lock does not contain version 2.9.0"
    exit 1
  fi
fi

Length of output: 180

---

Lockfile Updated Successfully

The package-lock.json has been updated to version 2.9.0. No yarn.lock file is present in the repository. No further changes are required.

CHANGELOG.md (1)

5-17: Changelog entry looks good.

The new 2.9.0 section follows the existing format, clearly describes the LiveObjects feature, includes the documentation link, and references PR #2007.