Skip to content

Release v2.11.0#2069

Merged
VeskeR merged 2 commits into
mainfrom
release/2.11.0
Aug 13, 2025
Merged

Release v2.11.0#2069
VeskeR merged 2 commits into
mainfrom
release/2.11.0

Conversation

@VeskeR
Copy link
Copy Markdown
Contributor

@VeskeR VeskeR commented Aug 13, 2025

#2060 had a public interface change, but as per 318fc5e commit message those fields were added prematurely and were not actually used so I decided not to include this change in the changelog as those fields were never mentioned before.

Summary by CodeRabbit

  • New Features

    • LiveMap now supports getting and setting JSON-encodable objects as entry values, enabling richer data handling.
  • Chores

    • Bumped version to 2.11.0.
    • Updated changelog with the 2.11.0 release entry.
    • Updated reported library version in the React Hooks agent string.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Aug 13, 2025

Walkthrough

Version updated to 2.11.0 across package metadata and React hooks export; CHANGELOG updated with a new release entry noting LiveMap JSON-encodable object support.

Changes

Cohort / File(s) Summary
Version bump
package.json, src/platform/react-hooks/src/AblyReactHooks.ts
Updated version from 2.10.1 to 2.11.0; adjusted exported version constant used in agent string.
Changelog
CHANGELOG.md
Added release entry for 2.11.0 (2025-08-13) mentioning LiveMap JSON-encodable object support (PR #2052).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

Thump-thump goes my fluffy heart—2.11.0 hops in!
I twitch my nose at versions, neatly pinned.
A changelog nibble, a semantic grin,
Agent string updated—let the sprint begin!
Carrot to the future—ship it, let’s win! 🥕🚀

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch release/2.11.0

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
🪧 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 bef0fff and bb896cb.

⛔ 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-browser (chromium)
  • GitHub Check: test-node (16.x)
  • GitHub Check: test-browser (firefox)
  • GitHub Check: test-node (20.x)
  • GitHub Check: test-browser (webkit)
  • GitHub Check: test-node (18.x)
  • GitHub Check: test-npm-package
🔇 Additional comments (3)
package.json (1)

4-4: Version bump to 2.11.0 looks good.

Matches the release intent and related changes. No issues spotted here.

CHANGELOG.md (1)

5-8: Changelog entry for 2.11.0 looks correct and concise.

Release date, tag link, and PR reference are consistent with the version bump.

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

15-15: React Hooks version constant updated to 2.11.0 — agent string will correctly emit react-hooks/2.11.0.

Change is minimal and correct.

export type ChannelParameters = string | ChannelNameAndOptions;

export const version = '2.10.1';
export const version = '2.11.0';
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Verify all version surfaces are synchronized (no lingering 2.10.1, and subpackage manifests match).

To avoid version drift in published artifacts and Ably-Agent headers, verify:

  • No remaining references to 2.10.1 exist.
  • The React Hooks version constant matches package.json.
  • The react subpackage manifests used during build are aligned.

Run this script from repo root:


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "1) Comparing package.json version with AblyReactHooks.ts constant..."
PKG_VERSION=$(jq -r '.version' package.json)
HOOKS_FILE="src/platform/react-hooks/src/AblyReactHooks.ts"
if [ ! -f "$HOOKS_FILE" ]; then
  echo "ERROR: $HOOKS_FILE not found"; exit 2
fi
HOOKS_VERSION=$(sed -nE "s/^\s*export const version = '([^']+)';/\1/p" "$HOOKS_FILE" | head -n1)
echo "package.json: $PKG_VERSION"
echo "AblyReactHooks.ts: ${HOOKS_VERSION:-<not found>}"
test -n "$HOOKS_VERSION" || { echo "ERROR: Could not extract version from $HOOKS_FILE"; exit 3; }
if [ "$PKG_VERSION" != "$HOOKS_VERSION" ]; then
  echo "ERROR: Version mismatch (package.json=$PKG_VERSION, AblyReactHooks.ts=$HOOKS_VERSION)"; exit 4
fi

echo
echo "2) Checking React subpackage manifest templates used by build (res/)..."
RES_DIR="src/platform/react-hooks/res"
if [ -d "$RES_DIR" ]; then
  MISMATCH=0
  while IFS= read -r -d '' f; do
    v=$(jq -r '.version // empty' "$f" 2>/dev/null || true)
    if [ -n "$v" ]; then
      printf "%s -> version=%s\n" "$f" "$v"
      if [ "$v" != "$PKG_VERSION" ]; then
        echo "WARN: Version mismatch in $f (expected $PKG_VERSION)"
        MISMATCH=1
      fi
    fi
  done < <(fd -0 -a 'package.*.json' "$RES_DIR")
  if [ "$MISMATCH" -ne 0 ]; then
    echo "ERROR: One or more res package.*.json versions do not match $PKG_VERSION"; exit 5
  fi
else
  echo "NOTE: $RES_DIR not found; skipping res manifests check."
fi

echo
echo "3) Scanning for lingering references to previous version (2.10.1)..."
if rg -n "\b2\.10\.1\b" -g '!**/node_modules/**' -g '!**/dist/**' -g '!**/build/**'; then
  echo "ERROR: Found lingering references to 2.10.1 (see matches above)"; exit 6
else
  echo "OK: No lingering references to 2.10.1 found."
fi

echo
echo "All version checks passed."

Length of output: 1072


🏁 Script executed:

#!/usr/bin/env bash
set -euo pipefail

echo "Verifying React Hooks subpackage manifests..."
RES_DIR="src/platform/react-hooks/res"
PKG_VERSION=$(jq -r .version package.json)

if [ -d "$RES_DIR" ]; then
  files=$(find "$RES_DIR" -type f -name 'package.*.json')
  if [ -z "$files" ]; then
    echo "No manifest templates found in $RES_DIR"
  else
    for f in $files; do
      v=$(jq -r '.version // empty' "$f" 2>/dev/null)
      echo "$f -> version=${v:-<none>}"
      if [ -n "$v" ] && [ "$v" != "$PKG_VERSION" ]; then
        echo "ERROR: Version mismatch in $f (expected $PKG_VERSION, got $v)"
        exit 1
      fi
    done
  fi
else
  echo "NOTE: $RES_DIR not found; skipping res manifests check."
fi

echo
echo "Scanning for lingering 2.10.1 references..."
if rg -n '\b2\.10\.1\b' -g '!**/node_modules/**' -g '!**/dist/**' -g '!**/build/**'; then
  echo "ERROR: Found lingering references to 2.10.1"
  exit 1
else
  echo "OK: No lingering 2.10.1 references found."
fi

echo
echo "Verification complete."

Length of output: 1764


Align React-Hooks subpackage manifests and update CHANGELOG for v2.11.0

  • src/platform/react-hooks/res/package.cjs.json, package.mjs.json, package.react.json
    • Add a "version": "2.11.0" field to each manifest so they match package.json.
  • CHANGELOG.md
    • Insert a new ## [2.11.0] – YYYY-MM-DD release heading (with your release notes) above the existing ## [2.10.1] section.
    • This ensures there are no stale 2.10.1 references at the top level.
  • Verified:
    • package.json and AblyReactHooks.ts both export version 2.11.0.
🤖 Prompt for AI Agents
In src/platform/react-hooks/src/AblyReactHooks.ts around line 15, the file
exports version '2.11.0' but the subpackage manifest files under
src/platform/react-hooks/res (package.cjs.json, package.mjs.json,
package.react.json) are missing or not updated with a "version": "2.11.0" field
and the top-level CHANGELOG.md lacks a new ## [2.11.0] – YYYY-MM-DD heading;
update each of the three manifest JSON files to include "version": "2.11.0" so
they match package.json and AblyReactHooks.ts, and insert a new release heading
`## [2.11.0] – YYYY-MM-DD` with your release notes above the existing `##
[2.10.1]` section in CHANGELOG.md.

@VeskeR VeskeR merged commit c923b2e into main Aug 13, 2025
12 of 14 checks passed
@VeskeR VeskeR deleted the release/2.11.0 branch August 13, 2025 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants