Skip to content

chore(master): release 2.0.0-rc.208#1236

Merged
devsergiy merged 1 commit intomasterfrom
release-please--branches--master--components--graphql-go-tools
Jul 21, 2025
Merged

chore(master): release 2.0.0-rc.208#1236
devsergiy merged 1 commit intomasterfrom
release-please--branches--master--components--graphql-go-tools

Conversation

@StarpTech
Copy link
Copy Markdown
Collaborator

@StarpTech StarpTech commented Jul 17, 2025

🤖 I have created a release beep boop

2.0.0-rc.208 (2025-07-18)

Features

Bug Fixes

  • check that object claims to implement interface (#1235) (5afbc68)
  • use NodeFragmentIsAllowedOnNode to check fragmentSpread (#1223) (e448c81)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

  • New Features

    • Introduced a depth limit to the parser.
  • Bug Fixes

    • Fixed an issue where objects did not properly claim to implement interfaces.
    • Improved fragment spread validation for more accurate results.
  • Documentation

    • Added a changelog entry for version 2.0.0-rc.208.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 17, 2025

Walkthrough

The version string for the "v2" release was incremented from "2.0.0-rc.207" to "2.0.0-rc.208" in the manifest file. Additionally, the changelog was updated to document the new release, noting one new feature (parser depth limit) and two bug fixes: interface implementation claim and fragment spread validation.

Changes

Files Change Summary
release-please-manifest.json Updated "v2" version from "2.0.0-rc.207" to "2.0.0-rc.208".
v2/CHANGELOG.md Added 2.0.0-rc.208 release entry with one new feature (parser depth limit) and two bug fixes (interface claim, fragment spread validation).

Possibly related PRs


📜 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 2aa00a1 and fdb11d5.

📒 Files selected for processing (2)
  • release-please-manifest.json (1 hunks)
  • v2/CHANGELOG.md (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • release-please-manifest.json
  • 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). (2)
  • GitHub Check: Build and test (go 1.23 / windows-latest)
  • GitHub Check: Build and test (go 1.23 / windows-latest)

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@StarpTech StarpTech force-pushed the release-please--branches--master--components--graphql-go-tools branch from 1368274 to 2aa00a1 Compare July 17, 2025 12:39
@StarpTech StarpTech force-pushed the release-please--branches--master--components--graphql-go-tools branch from 2aa00a1 to fdb11d5 Compare July 18, 2025 16:55
@devsergiy devsergiy merged commit d79e420 into master Jul 21, 2025
12 checks passed
@devsergiy devsergiy deleted the release-please--branches--master--components--graphql-go-tools branch July 21, 2025 14:36
@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