chore(master): release 2.0.0-rc.196

[StarpTech]

🤖 I have created a release beep boop

2.0.0-rc.196 (2025-07-02)

Features

• pass in response body (#1203) (ef03374)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• New Features
  • Added the ability to pass in a response body.

[coderabbitai]

Walkthrough

The version in the release manifest was incremented from 2.0.0-rc.195 to 2.0.0-rc.196, and a new entry was added to the changelog documenting the addition of a "pass in response body" feature associated with issue #1203 and commit ef03374.

Changes

Files	Change Summary
release-please-manifest.json	Updated "v2" version from 2.0.0-rc.195 to 2.0.0-rc.196.
v2/CHANGELOG.md	Added changelog entry for 2.0.0-rc.196 with new feature description.

Possibly related PRs

• chore(master): release 2.0.0-rc.195 #1202: Updates the version to 2.0.0-rc.195 and adds a changelog entry for a bug fix, similar in scope and file changes to this PR but for the previous release.

---

📜 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 ef03374 and 19f57ea.

📒 Files selected for processing (2)

• release-please-manifest.json (1 hunks)
• v2/CHANGELOG.md (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

v2/CHANGELOG.md (1)

Learnt from: SkArchon
PR: wundergraph/graphql-go-tools#1203
File: v2/pkg/engine/resolve/loader.go:63-67
Timestamp: 2025-07-02T15:28:02.073Z
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.

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Build and test (go 1.23 / windows-latest)
• GitHub Check: Build and test (go 1.23 / windows-latest)

🔇 Additional comments (2)

release-please-manifest.json (1)

2-2: Version bump looks correct and consistent with the tag.

The manifest now advertises 2.0.0-rc.196, matching the newly-added changelog section. Nothing else changed, so this is safe to merge.

v2/CHANGELOG.md (1)

3-9: Changelog entry is present and well-formatted.

The new 2.0.0-rc.196 section correctly lists the single feature with issue/commit references and follows the existing structure. No action required.

---

🪧 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]

🤖 Created releases:

• v2.0.0-rc.196

🌻