chore(master): release 2.0.0-rc.223

[StarpTech]

🤖 I have created a release beep boop

2.0.0-rc.223 (2025-08-28)

Features

• improved subscription heartbeats (#1269) (4423d60)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• Documentation

  • Added changelog entry for 2.0.0-rc.223 (2025-08-28), highlighting improved subscription heartbeats with references to the related issue and commit.
  • Existing changelog entries remain intact; changes are additive.

• Chores

  • Updated the public release manifest to reference v2 version 2.0.0-rc.223 (execution version unchanged).
  • No code, UI, or behavior changes included in this PR.

[coderabbitai]

Walkthrough

Bumps v2 release version in release-please-manifest.json from 2.0.0-rc.222 to 2.0.0-rc.223 and adds a corresponding 2.0.0-rc.223 entry to v2/CHANGELOG.md. No code or behavior changes; execution field unchanged.

Changes

Cohort / File(s)	Summary of changes
Release metadata `release-please-manifest.json`	Updated `v2` from `"2.0.0-rc.222"` to `"2.0.0-rc.223"`; `execution` remains `"1.4.0"`.
Documentation (Changelog) `v2/CHANGELOG.md`	Added new entry for `2.0.0-rc.223` (2025-08-28) with a Features bullet for improved subscription heartbeats; additive only.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore(master): release 2.0.0-rc.220 #1270 — Similar release metadata and v2 changelog updates for a different version.
• chore(master): release 2.0.0-rc.222 #1284 — Prior step bumping v2 from rc.221 to rc.222 in the same manifest.
• chore(master): release 2.0.0-rc.210 #1247 — Updates the same v2 entry in release-please-manifest.json and adds a v2 changelog entry for another release.

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release-please--branches--master--components--graphql-go-tools

---

🪧 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 @coderabbit in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbit 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:
  • @coderabbit gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbit 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 @coderabbit help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbit ignore or @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbit summary or @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbit or @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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 4423d60 and b458d12.

📒 Files selected for processing (2)

• release-please-manifest.json (1 hunks)
• v2/CHANGELOG.md (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). (2)

• GitHub Check: Build and test (go 1.23 / ubuntu-latest)
• GitHub Check: Build and test (go 1.23 / windows-latest)

🔇 Additional comments (3)

release-please-manifest.json (1)

2-2: LGTM: version bump aligns with the CHANGELOG entry.

v2/CHANGELOG.md (2)

3-9: LGTM: new 2.0.0-rc.223 entry is correctly dated (2025-08-28) and references #1269 and commit 4423d60.

---

3-9: CHANGELOG link and anchor formatting is correct.

[StarpTech]

🤖 Created releases:

• v2.0.0-rc.223

🌻