Update varfish-cli to 0.6.4

[BiocondaBot]

Update varfish-cli: 0.6.3 → 0.6.4

Info	Link or Description
Recipe	recipes/varfish-cli (click to view/edit other files)
Summary	Command line interface to VarFish via REST API
Home	https://github.com/bihealth/varfish-cli
Releases	https://pypi.org/pypi/varfish_cli/json

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

📝 Walkthrough

Walkthrough

The pull request involves updates to the meta.yaml file for the varfish-cli package. Key changes include an increment in the version number from "0.6.3" to "0.6.4" and an update to the SHA256 checksum, changing it to a new value. Additionally, the build number has been reset from 2 to 0. The build script remains unchanged, continuing to utilize Python's pip for installation without dependencies and maintaining build isolation. The requirements section has been updated to include setuptools as a host dependency, while the run dependencies remain consistent with the previous version to ensure compatibility with Python 3 and relevant libraries. The test section continues to include the same import and command for testing the package functionality. Finally, the about section retains the same metadata, including the home URL, license information, and summary description.

Possibly related PRs

• Update sawfish to 0.12.5 #51392: Updates the meta.yaml file for the sawfish package, involving version and SHA256 checksum changes.
• Update sawfish to 0.12.6 #51439: Similar to the main PR, this PR updates the meta.yaml file for the sawfish package, including changes to the version number and SHA256 checksum.
• Bump pyfastani to v0.6.0 #51550: Updates the meta.yaml file for the pyfastani package, including a version bump and SHA256 checksum change.
• Update clinvar-this to 0.18.3 #51560: Updates the meta.yaml file for the clinvar-this package, reflecting changes to the version and SHA256 checksum.
• Update crabs to 1.0.4 #51645: Modifies the meta.yaml file for the crabs package, updating the version and SHA256 checksum.
• Update oakvar to 2.11.24 #51678: Updates the meta.yaml file for the oakvar package, involving changes to the version and SHA256 checksum.
• Update oakvar to 2.11.25 #51839: Updates the oakvar package's meta.yaml file, including a version bump and SHA256 checksum update.
• Update oakvar to 2.11.26 #51944: Updates the oakvar package's meta.yaml file with a version increment and SHA256 checksum change.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between f46a5ed and 03fbe8b.

📒 Files selected for processing (1)

• recipes/varfish-cli/meta.yaml (3 hunks)

🧰 Additional context used

🪛 yamllint

recipes/varfish-cli/meta.yaml

[error] 1-1: syntax error: found character '%' that cannot start any token

(syntax)

🔇 Additional comments (4)

recipes/varfish-cli/meta.yaml (4)

14-14: LGTM! Build number reset follows best practices.

Resetting the build number to 0 for a new version is the correct approach.

---

25-25: LGTM! Adding setuptools as a host dependency is appropriate.

The addition of setuptools as a host dependency is correct as it's required for building Python packages, especially when using pip install.

---

Line range hint 1-58: Overall recipe structure and dependencies look good.

The recipe maintains proper structure and dependency specifications:

• Appropriate Python version constraints
• Properly pinned dependencies
• Maintained noarch: python setting
• Clear entry points and run exports

The changes are minimal and follow Conda packaging best practices.

---

1-2: Verify package checksum from PyPI.

The version bump follows semantic versioning. Let's verify the SHA256 checksum matches the published package.

🧰 Tools

🪛 yamllint

[error] 1-1: syntax error: found character '%' that cannot start any token

(syntax)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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