chore(master): release 2.0.0-rc.225

[StarpTech]

🤖 I have created a release beep boop

2.0.0-rc.225 (2025-09-09)

Features

• add support of field selection reasons extensions (#1282) (37c9582)
• upgrade all components to go 1.25 (#1289) (6bd2713)

Bug Fixes

• refactor CoordinateDependencies, FetchReasons (#1293) (cfebc16)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• New Features

  • Added support for field selection reasons extensions.
  • Upgraded all components to Go 1.25 for improved compatibility and performance.

• Chores

  • Bumped release version to 2.0.0-rc.225.

• Documentation

  • Updated changelog with a new 2.0.0-rc.225 entry detailing recent features.

[coderabbitai]

Walkthrough

Bumps v2 in release-please-manifest.json from 2.0.0-rc.224 → 2.0.0-rc.225 and prepends a v2/CHANGELOG.md entry for 2.0.0-rc.225 listing two Features: field selection reasons extensions and upgrading components to Go 1.25.

Changes

Cohort / File(s)	Summary of changes
Release bump & changelog (v2) release-please-manifest.json, v2/CHANGELOG.md	Updated manifest v2 version to 2.0.0-rc.225; added top changelog entry 2.0.0-rc.225 with Features: "add support of field selection reasons extensions" (PR #1282 / commit 37c9582) and "upgrade all components to go 1.25" (PR #1289 / commit 6bd2713).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore(master): release 2.0.0-rc.214 #1255 — Modifies the same v2 release metadata and changelog files; similar release bump pattern.
• chore(master): release 2.0.0-rc.205 #1226 — Performs a v2 release bump and adds a v2/CHANGELOG.md entry touching the same files.
• chore(master): release 2.0.0-rc.223 #1285 — Another RC bump updating release-please-manifest.json v2 and v2/CHANGELOG.md.

Pre-merge checks (3 passed)

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title clearly and concisely conveys the primary purpose of the changeset—publishing version 2.0.0-rc.225—without extraneous detail, making it immediately clear to reviewers that this is a release chore.
Description Check	✅ Passed	The description directly reflects the content of the changeset by summarizing the new version, linking the comparison range, and listing the added features and bug fixes, so it is clearly related and informative.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 814ece2 and cee0d21.

📒 Files selected for processing (2)

• release-please-manifest.json (1 hunks)
• v2/CHANGELOG.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (2)

• release-please-manifest.json
• v2/CHANGELOG.md

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

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

v2/CHANGELOG.md (1)

3-9: Consider calling out minimum toolchain explicitly and tweak wording.

• Optional: add a brief note like “Requires Go ≥1.25” under a “BREAKING CHANGES” or “Chores” note if this raises the minimum supported Go for consumers.
• Optional: capitalize “Go” for consistency with common style.

If you want, I can propose a tiny patch to insert a one-liner note under this entry.

📜 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 6bd2713 and 90775ac.

📒 Files selected for processing (2)

• release-please-manifest.json (1 hunks)
• v2/CHANGELOG.md (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-08-29T09:35:47.969Z

Learnt from: ysmolski
PR: wundergraph/graphql-go-tools#1282
File: v2/pkg/engine/plan/visitor.go:5-5
Timestamp: 2025-08-29T09:35:47.969Z
Learning: The wundergraph/graphql-go-tools project does not support Go versions < 1.23, so compatibility concerns for features available in Go 1.21+ (like cmp.Or) should not be raised.

Applied to files:

• v2/CHANGELOG.md

⏰ 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: Verify Go 1.25 consistency All go.mod files (root, v2/, execution/, examples/federation/) specify Go 1.25; no GitHub Actions workflows using setup-go@ or go-version entries were found—please confirm none exist or update accordingly; no Dockerfiles with Golang base images detected—please verify if any are present.

v2/CHANGELOG.md (1)

3-9: Changelog entry reads well; links/date align with 2025-09-05.

Entry, compare range, and references look correct.

[StarpTech]

🤖 Created releases:

• v2.0.0-rc.225

🌻