chore(master): release 2.0.0-rc.236

[StarpTech]

🤖 I have created a release beep boop

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

Bug Fixes

• fix conflict of rewriter and required fields (#1338) (03189bc)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

Release Notes

• Bug Fixes
  • Resolved conflict between rewriter and required fields

[coderabbitai]

Walkthrough

Release candidate version bump from 2.0.0-rc.235 to 2.0.0-rc.236 with corresponding changelog entry documenting a bug fix for rewriter and required fields conflict resolution.

Changes

Cohort / File(s)	Summary
Release manifest update release-please-manifest.json	Updated v2 version constant from 2.0.0-rc.235 to 2.0.0-rc.236; execution version remains at 1.6.0
Changelog entry v2/CHANGELOG.md	Added new changelog section for version 2.0.0-rc.236 (2025-10-31) documenting bug fix for rewriter and required fields conflict (issue #1338)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

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 pull request title "chore(master): release 2.0.0-rc.236" is directly and fully related to the main changes in the changeset. The PR updates the release manifest and adds a changelog entry to create version 2.0.0-rc.236, which is exactly what the title communicates. The title is concise, uses appropriate conventional commit format (chore with scope), and clearly conveys the primary purpose of the PR. A teammate scanning the git history would immediately understand that this is a release operation for a specific version without ambiguity.

✨ 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 03189bc and 5e5f2a5.

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

🔇 Additional comments (2)

release-please-manifest.json (1)

2-2: Version bump is correctly applied.

The release manifest is properly updated to reflect the new RC version while maintaining the separate execution component version.

v2/CHANGELOG.md (1)

3-9: Changelog entry is correctly formatted and structured.

The new release entry follows the established changelog convention with proper versioning, date, issue/commit references, and markdown links.

---

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

[StarpTech]

🤖 Created releases:

• v2.0.0-rc.236

🌻