chore(master): release 2.0.0-rc.241

[StarpTech]

🤖 I have created a release beep boop

2.0.0-rc.241 (2025-12-10)

Bug Fixes

• group subgraph errors by subgraph name (#1351) (d65d348)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• Bug Fixes
  • Fixed an issue where subgraph errors are now properly grouped by subgraph name in v2.0.0-rc.241.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Version bump of v2 release candidate from 2.0.0-rc.240 to 2.0.0-rc.241 in the release manifest, with corresponding changelog entry documenting a subgraph error grouping fix.

Changes

Cohort / File(s)	Summary
Release manifest version update release-please-manifest.json	Updated v2 field from "2.0.0-rc.240" to "2.0.0-rc.241"
Changelog entry v2/CHANGELOG.md	Added release notes for 2.0.0-rc.241 (2025-12-10) documenting bug fix: grouping subgraph errors by subgraph name

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore(master): release 2.0.0-rc.240 #1349: Sequential release candidate version bumps with corresponding changelog updates
• chore(master): release 2.0.0-rc.233 #1333: Consecutive v2 field updates in release-please-manifest.json
• chore(master): release 2.0.0-rc.223 #1285: Identical pattern of manifest version bump paired with v2/CHANGELOG.md 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.241' clearly and specifically identifies the release version and accurately reflects the changeset's primary purpose of releasing version 2.0.0-rc.241.

✨ 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 d65d348 and f246071.

📒 Files selected for processing (2)

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

🧰 Additional context used

🧠 Learnings (3)

📓 Common learnings

Learnt from: ysmolski
Repo: wundergraph/graphql-go-tools PR: 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.

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

Learnt from: ysmolski
Repo: wundergraph/graphql-go-tools PR: 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

📚 Learning: 2025-12-09T15:30:57.980Z

Learnt from: SkArchon
Repo: wundergraph/graphql-go-tools PR: 1351
File: v2/pkg/engine/resolve/context.go:160-162
Timestamp: 2025-12-09T15:30:57.980Z
Learning: In the graphql-go-tools repository, Context instances in v2/pkg/engine/resolve must be created using NewContext() rather than Context{} literals. The codebase intentionally avoids defensive nil checks for Context.subgraphErrors to enforce this pattern and fail fast on improper usage. Do not suggest adding defensive nil checks for map fields in Context that are initialized by NewContext().

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 / ubuntu-latest)
• 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)

🔇 Additional comments (2)

v2/CHANGELOG.md (1)

3-8: Release entry looks good.

The changelog entry for v2.0.0-rc.241 is properly formatted with correct version link, date, and bug fix documentation including issue and commit references.

release-please-manifest.json (1)

2-2: Version bump is consistent with changelog.

The manifest correctly bumps v2 from 2.0.0-rc.240 to 2.0.0-rc.241, aligned with the changelog entry.

---

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

[StarpTech]

🤖 Created releases:

• v2.0.0-rc.241

🌻