chore(master): release 2.0.0-rc.234

[StarpTech]

🤖 I have created a release beep boop

2.0.0-rc.234 (2025-10-24)

Features

• september 2025 spec description support for OperationDocument and Fragment (#1331) (aedaf71)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• New Features
  • Added support for September 2025 specification descriptions.

[coderabbitai]

Walkthrough

Updated the v2 release manifest from "2.0.0-rc.233" to "2.0.0-rc.234" and added a new changelog entry documenting September 2025 spec description support for OperationDocument and Fragment with timestamp 2025-10-24.

Changes

Cohort / File(s)	Summary
Release Files release-please-manifest.json, v2/CHANGELOG.md	Version bump in manifest (2.0.0-rc.233 → 2.0.0-rc.234); new changelog entry for rc.234 documenting spec description support feature.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• chore(master): release 2.0.0-rc.223 #1285: Both PRs modify the same release files (release-please-manifest.json v2 version and v2/CHANGELOG.md entries) updating the v2 release tag to a new rc version.
• chore(master): release 2.0.0-rc.230 #1317: Both PRs perform automated release updates modifying the same release-please-manifest.json v2 version entry and v2/CHANGELOG.md with release-bump changes.
• chore(master): release 2.0.0-rc.220 #1270: Both PRs update the same files—bumping the v2 entry in release-please-manifest.json and adding a new v2/CHANGELOG.md release entry.

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 title "chore(master): release 2.0.0-rc.234" directly and accurately describes the primary change in the pull request. The changeset consists of bumping the version from 2.0.0-rc.233 to 2.0.0-rc.234 in the manifest file and adding a corresponding changelog entry, which is exactly what the title conveys. The title is concise, uses the conventional commit format appropriately for a release, includes the specific version number, and is clear enough that a teammate reviewing git history would immediately understand this is a release commit.

✨ 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 aedaf71 and 5959b1b.

📒 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 / windows-latest)
• GitHub Check: Build and test (go 1.25 / ubuntu-latest)

🔇 Additional comments (2)

release-please-manifest.json (1)

1-4: Version bump looks good.

The manifest has been correctly updated to version 2.0.0-rc.234 with the execution version remaining at 1.6.0, consistent with patch-level release candidate progression.

v2/CHANGELOG.md (1)

3-8: Changelog entry is well-formatted.

The new release entry for 2.0.0-rc.234 follows the established pattern with proper formatting, correct GitHub compare link, clear feature description, and valid issue/commit references.

---

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

[StarpTech]

🤖 Created releases:

• v2.0.0-rc.234

🌻