chore(master): release 2.0.0-rc.195

[StarpTech]

🤖 I have created a release beep boop

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

Bug Fixes

• fix checking presence of type mapping to interface object (#1201) (0a849ee)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• Bug Fixes

  • Resolved an issue with checking the presence of type mapping to interface objects.

• Documentation

  • Added a changelog entry for version 2.0.0-rc.195, detailing the latest bug fix.

[coderabbitai]

Walkthrough

The version in the release manifest was incremented to 2.0.0-rc.195, and a corresponding changelog entry was added describing a bug fix related to type mapping to interface objects. No changes were made to exported or public entities.

Changes

Files	Change Summary
release-please-manifest.json	Updated "v2" version from 2.0.0-rc.194 to 2.0.0-rc.195
v2/CHANGELOG.md	Added entry for 2.0.0-rc.195: documents bug fix for type mapping to interface objects (issue #1201)

---

📜 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 0a849ee and 6154058.

📒 Files selected for processing (2)

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

⏰ 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

v2 moves from 2.0.0-rc.194 ➞ 2.0.0-rc.195, matching the changelog entry. Nothing else to flag.

v2/CHANGELOG.md (1)

3-9: Changelog entry consistent and properly linked

Entry follows the existing structure (heading, date, “Bug Fixes” section, issue & commit links). No discrepancies spotted.

---

🪧 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.195

🌻