Skip to content

chore(master): release 2.0.0-rc.238#1344

Merged
ysmolski merged 1 commit intomasterfrom
release-please--branches--master--components--graphql-go-tools
Nov 17, 2025
Merged

chore(master): release 2.0.0-rc.238#1344
ysmolski merged 1 commit intomasterfrom
release-please--branches--master--components--graphql-go-tools

Conversation

@StarpTech
Copy link
Copy Markdown
Collaborator

@StarpTech StarpTech commented Nov 17, 2025

🤖 I have created a release beep boop

2.0.0-rc.238 (2025-11-17)

Bug Fixes

  • add ability to exclude introspection queries from complexity limits (#1342) (19c8693)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

  • Bug Fixes
    • Fixed an issue that prevented introspection queries from being properly excluded from complexity limits.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Nov 17, 2025

Walkthrough

Bumps the v2 prerelease version identifier from 2.0.0-rc.237 to 2.0.0-rc.238 in release-please-manifest.json, and adds a corresponding changelog entry documenting a bug fix for excluding introspection queries from complexity limits.

Changes

Cohort / File(s) Summary
Release metadata and changelog
release-please-manifest.json, v2/CHANGELOG.md
Updates v2 prerelease version to 2.0.0-rc.238 and adds changelog entry documenting introspection query exclusion bugfix dated 2025-11-17

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

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 summarizes the main change—it's a release commit for version 2.0.0-rc.238, which matches the version bumps in the manifest and changelog entries.
✨ 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 19c8693 and 421c214.

📒 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). (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 correct and consistent.

v2/CHANGELOG.md (1)

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

The entry for 2.0.0-rc.238 follows the project's conventional commit format, includes proper version comparison links, and correctly references the associated issue and commit.


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

@ysmolski ysmolski merged commit bcf604f into master Nov 17, 2025
11 checks passed
@ysmolski ysmolski deleted the release-please--branches--master--components--graphql-go-tools branch November 17, 2025 08:37
@StarpTech
Copy link
Copy Markdown
Collaborator 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