Skip to content

chore(master): release 2.0.0-rc.226#1296

Merged
devsergiy merged 1 commit into
masterfrom
release-please--branches--master--components--graphql-go-tools
Sep 12, 2025
Merged

chore(master): release 2.0.0-rc.226#1296
devsergiy merged 1 commit into
masterfrom
release-please--branches--master--components--graphql-go-tools

Conversation

@StarpTech

@StarpTech StarpTech commented Sep 12, 2025

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

2.0.0-rc.226 (2025-09-12)

Bug Fixes


This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

  • Bug Fixes

    • Correctly detect "requires" on interface members, improving accuracy in dependency/interface validation scenarios.
  • Documentation

    • Updated changelog with entry for version 2.0.0-rc.226 detailing the bug fix.
  • Chores

    • Bumped release version to 2.0.0-rc.226.

@coderabbitai

coderabbitai Bot commented Sep 12, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

Bumps v2 version in release-please-manifest.json from 2.0.0-rc.225 to 2.0.0-rc.226 and adds a corresponding 2.0.0-rc.226 entry to v2/CHANGELOG.md noting a bug fix.

Changes

Cohort / File(s) Summary of Changes
Release metadata
release-please-manifest.json
Updated v2 field value from "2.0.0-rc.225" to "2.0.0-rc.226"; execution remains "1.4.0".
Changelog update
v2/CHANGELOG.md
Added new entry for 2.0.0-rc.226 (2025-09-12) with a bug fix note; placed above prior rc.225 entry.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Pre-merge checks (3 passed)

✅ 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.226" is concise, follows conventional-commit style, and directly communicates the primary change (a release version bump to v2.0.0-rc.226), so a teammate scanning history will understand the purpose.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.

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.


📜 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 70bd5d5 and da074cd.

📒 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). (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)
v2/CHANGELOG.md (1)

3-9: LGTM: entry matches PR details and formatting remains consistent.

Date, compare link, issue, and commit hash align with the PR summary.

release-please-manifest.json (1)

2-2: LGTM: manifest bump aligns with changelog (rc.226).

No other fields changed; consistent with Release Please flow.


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

@devsergiy devsergiy merged commit 8686cb4 into master Sep 12, 2025
11 checks passed
@devsergiy devsergiy deleted the release-please--branches--master--components--graphql-go-tools branch September 12, 2025 11:32
@StarpTech

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants