chore(master): release 2.0.0-rc.227

[StarpTech]

🤖 I have created a release beep boop

2.0.0-rc.227 (2025-09-23)

Bug Fixes

• if blocked, defer async event insertion to prevent deadlocks (#1298) (df38c31)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• Bug Fixes
  • Resolved potential deadlocks by deferring async event insertion when operations are blocked, improving stability and responsiveness under load.
• Documentation
  • Updated changelog for version 2.0.0-rc.227.
• Chores
  • Bumped version to 2.0.0-rc.227.

[coderabbitai]

Walkthrough

Updates the release manifest to bump v2 from 2.0.0-rc.226 to 2.0.0-rc.227 and adds a corresponding changelog entry noting a bug fix about deferring async event insertion when blocked.

Changes

Cohort / File(s)	Change summary
Release manifest release-please-manifest.json	Bumps v2 version from 2.0.0-rc.226 to 2.0.0-rc.227.
Changelog v2/CHANGELOG.md	Adds entry for 2.0.0-rc.227 (2025-09-23) describing a bug fix: defers async event insertion when blocked to prevent deadlocks.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks

✅ Passed checks (3 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.227" succinctly and accurately summarizes the primary change—a release/version bump to v2.0.0-rc.227—and aligns with the PR objectives and the modified files (release-please-manifest.json and CHANGELOG). It is concise, specific, and follows conventional commit/release naming.
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 df38c31 and d246e5b.

📒 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 / 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: Approve: manifest v2 matches CHANGELOG top heading (2.0.0-rc.227).
No action required.

v2/CHANGELOG.md (1)

3-9: Changelog formatting OK — external refs couldn't be verified

Verification script returned 404 from GitHub compare API; cannot confirm compare range (v2.0.0-rc.226...v2.0.0-rc.227), issue #1298, or commit df38c31. File: v2/CHANGELOG.md (lines 3–9). Verify that both tags/releases exist and that issue #1298 and commit df38c31 are reachable, or re-run the verification script.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

[StarpTech]

🤖 Created releases:

• v2.0.0-rc.227

🌻