chore(master): release 2.0.0-rc.240

[StarpTech]

🤖 I have created a release beep boop

2.0.0-rc.240 (2025-12-04)

Features

• add composite type support for field resolvers (#1341) (701ea8d)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• New Features

  • Added composite type support for field resolvers, enabling enhanced type handling capabilities in resolver functions.

• Chores

  • Updated to version 2.0.0-rc.240.

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

[coderabbitai]

Walkthrough

This pull request bumps the v2 release version from 2.0.0-rc.239 to 2.0.0-rc.240 in the manifest and adds a corresponding changelog entry documenting composite type support for field resolvers.

Changes

Cohort / File(s)	Change Summary
Release Manifest release-please-manifest.json	Version bump for v2 from 2.0.0-rc.239 to 2.0.0-rc.240
Changelog v2/CHANGELOG.md	New changelog entry for v2.0.0-rc.240 (2025-12-04) documenting composite type support for field resolvers feature

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore(master): release 2.0.0-rc.210 #1247: Both PRs update release-please-manifest.json version entries and add corresponding v2 changelog release entries (automated release management).

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 accurately describes the main purpose of the PR: an automated release commit that bumps the version to 2.0.0-rc.240, which is the primary change across both modified files.

✨ 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 701ea8d and c1a8091.

📒 Files selected for processing (2)

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

🧰 Additional context used

🧠 Learnings (6)

📓 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-11-19T09:42:17.644Z

Learnt from: Noroth
Repo: wundergraph/graphql-go-tools PR: 1341
File: v2/pkg/engine/datasource/grpc_datasource/execution_plan_visitor_federation.go:406-429
Timestamp: 2025-11-19T09:42:17.644Z
Learning: In the wundergraph/graphql-go-tools gRPC datasource implementation (v2/pkg/engine/datasource/grpc_datasource), field resolvers must have arguments. The system does not currently support defining field resolvers without arguments. This invariant ensures that the `parentCallID` increment in `enterFieldResolver` is always matched by a decrement in `LeaveField` (which checks `r.operation.FieldHasArguments(ref)`).

Applied to files:

• v2/CHANGELOG.md

📚 Learning: 2025-12-02T08:25:26.682Z

Learnt from: Noroth
Repo: wundergraph/graphql-go-tools PR: 1341
File: v2/pkg/engine/datasource/grpc_datasource/execution_plan.go:1053-1118
Timestamp: 2025-12-02T08:25:26.682Z
Learning: In v2/pkg/engine/datasource/grpc_datasource field resolver response handling for composite types (interface/union), buildFieldResolverTypeMessage correctly combines both message.Fields and message.FieldSelectionSet: message.Fields contains interface-level fields that can be selected directly on the interface (such as __typename or fields defined in the interface itself), while message.FieldSelectionSet contains type-specific fields from inline fragments. This mixing is intentional and correct for GraphQL interfaces, as interface-level fields exist outside inline fragment selections and must be handled separately from type-specific fragment selections.

Applied to files:

• v2/CHANGELOG.md

📚 Learning: 2025-11-19T10:53:06.342Z

Learnt from: Noroth
Repo: wundergraph/graphql-go-tools PR: 1341
File: v2/pkg/engine/datasource/grpc_datasource/execution_plan.go:1039-1097
Timestamp: 2025-11-19T10:53:06.342Z
Learning: In v2/pkg/engine/datasource/grpc_datasource field resolver response handling, the `resolveRequiredFields` function intentionally uses two distinct approaches: for simple GraphQL object types it populates `message.Fields`, while for composite types (interface/union) it exclusively uses `message.FieldSelectionSet` with fragment-based selections. This differs from `buildFieldMessage` (regular queries) because field resolver responses returning composite types must align with protobuf oneOf structure, where all selections—including common interface fields—are handled through fragment selections built by `buildCompositeField`. The two approaches cannot be mixed in field resolver responses.

Applied to files:

• v2/CHANGELOG.md

📚 Learning: 2025-10-16T13:05:19.838Z

Learnt from: Noroth
Repo: wundergraph/graphql-go-tools PR: 1323
File: v2/pkg/engine/datasource/grpc_datasource/compiler.go:683-702
Timestamp: 2025-10-16T13:05:19.838Z
Learning: In GraphQL field resolver context resolution (v2/pkg/engine/datasource/grpc_datasource/compiler.go), when traversing paths in resolveContextDataForPath, the code can safely assume that intermediate path segments will only be messages or lists, never scalars. This is because field resolvers are only defined on GraphQL object types, not scalar types, so the parent function must return either a message or a list. This invariant is enforced by the GraphQL type system design.

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). (3)

• 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)

2-2: Version bump is consistent with CHANGELOG.md.

The manifest version correctly increments from 2.0.0-rc.239 to 2.0.0-rc.240, and the execution component remains at 1.6.0, which aligns with the automated release.

v2/CHANGELOG.md (1)

3-9: Changelog entry is well-formatted and accurate.

The new release entry for 2.0.0-rc.240 is properly structured with correct version comparisons, date, and feature attribution. The feature description accurately reflects the composite type support addition for field resolvers (issue #1341).

---

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