chore(master): release 2.0.0-rc.235

[StarpTech]

🤖 I have created a release beep boop

2.0.0-rc.235 (2025-10-29)

Bug Fixes

• improve query planning time (#1326) (373cf2a)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• Bug Fixes
  • Improved query planning time performance.

[coderabbitai]

Walkthrough

Automated release bump incrementing the v2 version from 2.0.0-rc.234 to 2.0.0-rc.235 in the release manifest. Corresponding changelog entry added documenting a bug fix related to query planning performance improvements.

Changes

Cohort / File(s)	Change Summary
Release Metadata release-please-manifest.json	Updated v2 version from 2.0.0-rc.234 to 2.0.0-rc.235
Changelog v2/CHANGELOG.md	Added new version entry 2.0.0-rc.235 with bug fix: "improve query planning time"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Release manifest version bumps and changelog entries are typically auto-generated and require only verification that the version number and entry format are correct.

Possibly related PRs

• chore(master): release 2.0.0-rc.226 #1296: Modifies release metadata files for a related rc release version bump
• chore(master): release 2.0.0-rc.233 #1333: Updates release-please-manifest.json and v2/CHANGELOG.md for rc version advancement
• chore(master): release 2.0.0-rc.223 #1285: Performs similar release bumps through release metadata updates

Suggested labels

autorelease: tagged

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The PR title "chore(master): release 2.0.0-rc.235" is fully related to the changeset. The pull request bumps the version in release-please-manifest.json from 2.0.0-rc.234 to 2.0.0-rc.235 and adds a corresponding changelog entry, which are exactly the changes expected from a release action. The title is concise, specific, and uses standard conventional commit formatting. A teammate reviewing the PR history would immediately understand that this is a release action for the specified version.

✨ Finishing touches

🧪 Generate unit tests (beta)

• 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

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 373cf2a and 406c113.

📒 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). (4)

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

🔇 Additional comments (2)

release-please-manifest.json (1)

2-2: Version bump looks correct.

The v2 version is correctly incremented from 2.0.0-rc.234 to 2.0.0-rc.235 (patch pre-release increment), and the execution component version remains stable at 1.6.0.

v2/CHANGELOG.md (1)

3-9: Changelog entry well‑formatted and properly linked.

The new 2.0.0-rc.235 section follows the established format with correct GitHub links (compare view, issue reference, commit hash). The bug fix description is concise and actionable.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[StarpTech]

🤖 Created releases:

• v2.0.0-rc.235

🌻