chore(master): release 2.0.0-rc.237

[StarpTech]

🤖 I have created a release beep boop

2.0.0-rc.237 (2025-10-31)

Features

• add support for field resolvers (#1323) (0e3c00f)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• Chores
  • Released version 2.0.0-rc.237
  • Updated changelog documenting support for field resolvers

[coderabbitai]

Walkthrough

This pull request bumps the release candidate version of v2 from 2.0.0-rc.236 to 2.0.0-rc.237 and adds a corresponding changelog entry documenting support for field resolvers.

Changes

Cohort / File(s)	Summary
Release Manifest & Changelog release-please-manifest.json, v2/CHANGELOG.md	Version bump from rc.236 to rc.237; added changelog entry for 2.0.0-rc.237 (2025-10-31) documenting new field resolver support feature

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore(master): release 2.0.0-rc.230 #1317 — Both update the same v2 manifest key and changelog for a new rc release
• chore(master): release 2.0.0-rc.226 #1296 — Both perform release bumps updating v2 manifest and changelog entries
• chore(master): release 2.0.0-rc.236 #1339 — Both bump the same rc.236 → rc.237 release-candidate version

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 PR title "chore(master): release 2.0.0-rc.237" is fully aligned with the changeset. The primary changes involve updating the manifest file to version 2.0.0-rc.237 and adding a corresponding changelog entry for that release. The title clearly and specifically identifies the main objective as a release of version 2.0.0-rc.237, using standard conventional commit formatting. It is concise, free from vague terminology or noise, and provides sufficient specificity that a teammate reviewing the Git history would immediately understand this is a release commit for a specific version.

✨ 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 0e3c00f and 5e5f697.

📒 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
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

⏰ 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 / 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 correct.

The manifest properly reflects the RC increment from 2.0.0-rc.236 to 2.0.0-rc.237, while keeping the execution component at 1.6.0.

v2/CHANGELOG.md (1)

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

The new rc.237 entry follows the established changelog format with proper GitHub links, commit references, and conventional commits categorization. Date, compare URL, and feature description are all in order.

---

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