Skip to content

chore(master): release 2.0.0-rc.217#1264

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

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

Conversation

@StarpTech
Copy link
Copy Markdown
Collaborator

@StarpTech StarpTech commented Aug 6, 2025

🤖 I have created a release beep boop

2.0.0-rc.217 (2025-08-06)

Bug Fixes

  • add an option to ignore skip/include directives (#1261) (dfd6523)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

  • Bug Fixes

    • Added an option to ignore skip/include directives in GraphQL processing.
  • Documentation

    • Updated the changelog with details for version 2.0.0-rc.217.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Aug 6, 2025

Walkthrough

This change updates the version string for the v2 release from 2.0.0-rc.216 to 2.0.0-rc.217 in the release manifest and adds a corresponding entry to the changelog documenting a bug fix related to GraphQL skip/include directives.

Changes

Cohort / File(s) Change Summary
Release Version Update
release-please-manifest.json
Updated the "v2" version from "2.0.0-rc.216" to "2.0.0-rc.217".
Changelog Update
v2/CHANGELOG.md
Added a new entry for version 2.0.0-rc.217 documenting a bug fix for skip/include directives.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
🧪 Generate unit tests
  • 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

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.
  • 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.

Support

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

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 generate unit tests to generate unit tests for 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.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
v2/CHANGELOG.md (1)

3-9: Minor formatting nit – keep list style consistent
All recent changelog sections use a leading space before the asterisk, e.g.

* generate query plans …

The new entry omits that leading space. For perfect consistency:

-* add an option to ignore skip/include directives ...
+* add an option to ignore skip/include directives ...
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dfd6523 and 074a308.

📒 Files selected for processing (2)
  • release-please-manifest.json (1 hunks)
  • v2/CHANGELOG.md (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: in the graphql-go-tools codebase, result structs are consistently initialized with non-nil bytes.buf...
Learnt from: SkArchon
PR: wundergraph/graphql-go-tools#1203
File: v2/pkg/engine/resolve/loader.go:63-67
Timestamp: 2025-07-02T15:28:02.122Z
Learning: In the graphql-go-tools codebase, result structs are consistently initialized with non-nil bytes.Buffer instances, making additional nil checks for res.out unnecessary defensive programming.

Applied to files:

  • v2/CHANGELOG.md
🔇 Additional comments (1)
release-please-manifest.json (1)

2-3: Version bump looks correct and consistent with the accompanying changelog
Nothing else to flag.

@ysmolski ysmolski merged commit a490fad into master Aug 6, 2025
11 checks passed
@ysmolski ysmolski deleted the release-please--branches--master--components--graphql-go-tools branch August 6, 2025 12:31
@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