chore(master): release 2.0.0-rc.220

[StarpTech]

🤖 I have created a release beep boop

2.0.0-rc.220 (2025-08-13)

Features

• rewrite abstract fragments for grpc (#1268) (ebe1e53)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• New Features
  • Enhanced gRPC integration for more reliable and maintainable behavior.
• Documentation
  • Updated changelog with the 2.0.0-rc.220 release entry.
• Chores
  • Bumped public manifest to version 2.0.0-rc.220.

[coderabbitai]

Walkthrough

Bumps v2 version in release-please-manifest.json from 2.0.0-rc.219 to 2.0.0-rc.220 and adds a corresponding 2.0.0-rc.220 entry to v2/CHANGELOG.md noting a feature “rewrite abstract fragments for grpc.” No other fields or files are changed.

Changes

Cohort / File(s)	Summary
Release metadata update release-please-manifest.json	Update v2 version string from "2.0.0-rc.219" to "2.0.0-rc.220"; execution stays at "1.4.0".
Changelog addition v2/CHANGELOG.md	Add new top entry for 2.0.0-rc.220 (2025-08-13) with a feature: rewrite abstract fragments for grpc.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• chore(master): release 2.0.0-rc.197 #1205: Similar release metadata update and changelog entry affecting v2.
• chore(master): release 2.0.0-rc.203 #1222: Another v2 release bump with corresponding changelog modifications.
• chore(master): release 2.0.0-rc.219 #1267: Successive update to v2 version and changelog (rc.219 → rc.220).

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

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

v2/CHANGELOG.md (1)

8-8: Capitalize gRPC for consistency.
Previous entries use “gRPC”; this new line uses “grpc”.

Apply this diff:

-* rewrite abstract fragments for grpc ([#1268](https://github.com/wundergraph/graphql-go-tools/issues/1268)) ([ebe1e53](https://github.com/wundergraph/graphql-go-tools/commit/ebe1e533aedc63b5970f476cb1bf37e88c6c21c4))
+* rewrite abstract fragments for gRPC ([#1268](https://github.com/wundergraph/graphql-go-tools/issues/1268)) ([ebe1e53](https://github.com/wundergraph/graphql-go-tools/commit/ebe1e533aedc63b5970f476cb1bf37e88c6c21c4))

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ebe1e53 and d0bb0a3.

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

🔇 Additional comments (2)

release-please-manifest.json (2)

2-2: Manifest bump looks correct and aligned with the changelog entry.
Version advanced to 2.0.0-rc.220 and no other fields changed. LGTM.

---

2-2: Sanity check passed: manifest and changelog are consistent.

• release-please-manifest.json v2 entry (2.0.0-rc.220) matches the top heading in v2/CHANGELOG.md.
• The comparison link correctly points from v2.0.0-rc.219…v2.0.0-rc.220.

[StarpTech]

🤖 Created releases:

• v2.0.0-rc.220

🌻