Update open-cravat to 2.9.0

[BiocondaBot]

Update open-cravat: 2.8.0 → 2.9.0

Info	Link or Description
Recipe	recipes/open-cravat (click to view/edit other files)
Summary	OpenCRAVAT - variant analysis toolkit
Home	https://www.opencravat.org
Releases	https://pypi.org/pypi/open-cravat/json
Recipe Maintainer(s)	@rkiminsilico

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates the meta.yaml file for the open-cravat package. It modifies the version number from "2.8.0" to "2.9.0" and changes the SHA-256 checksum to reflect the new source package. These updates ensure that the package version and its integrity verification hash are aligned with the latest release.

Changes

File	Change Summary
recipes/open-cravat/meta.yaml	Version updated from "2.8.0" to "2.9.0"; SHA256 checksum updated from 14759157660f2c46fd235947489cf73952a82e2340c9f588eb112190b415e18d to a2455799ead787a58f156c9e4b1250a948f484def4cd9a03b6c6bd6c9ea5edf1

Possibly related PRs

• Update gget to 0.29.0 #50960: The meta.yaml file for the gget package was updated with a new version and SHA256 checksum.
• Update architeuthis to 0.3.1 #50970: The meta.yaml file for the architeuthis package was updated with a new version and SHA256 checksum.
• Update stranger to 0.9.2 #50971: The meta.yaml file for the stranger package was updated with a new version and SHA256 checksum.
• Update kmertools to 0.1.4 #50972: The meta.yaml file for the kmertools package was updated with a new version and SHA256 checksum.
• Update vsearch to 2.29.0 #50975: The meta.yaml file for the vsearch package was updated with a new version and SHA256 checksum.
• Update peaks2utr to 1.3.2 #50979: The meta.yaml file for the peaks2utr package was updated with a new version and SHA256 checksum.
• Update repic to 1.0.0 #50989: The meta.yaml file for the repic package was updated with a new version and SHA256 checksum.
• Update phyloacc to 2.4.0 #50992: The meta.yaml file for the phyloacc package was updated with a new version and SHA256 checksum.
• Update genomedata to 1.7.3 #50995: The meta.yaml file for the genomedata package was updated with a new version and SHA256 checksum.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between ef1cf96 and e2f1e2a.

📒 Files selected for processing (1)

• recipes/open-cravat/meta.yaml (1 hunks)

🔇 Additional comments (3)

recipes/open-cravat/meta.yaml (3)

2-2: Version update looks good.

The version has been correctly updated from 2.8.0 to 2.9.0, which is consistent with the PR objectives.

---

Line range hint 1-67: Consider checking for potential dependency updates.

The version update from 2.8.0 to 2.9.0 might involve changes in dependencies. While the current meta.yaml file doesn't show any version-specific dependencies that would be affected by this update, it's worth verifying if any of the listed dependencies need to be updated or if any new dependencies need to be added for version 2.9.0 of open-cravat.

To check for potential dependency changes, you can compare the setup.py or requirements.txt files between versions 2.8.0 and 2.9.0 of the open-cravat package. Here's a script to help with this verification:

#!/bin/bash
# Description: Compare setup.py or requirements.txt between versions

# Function to download a specific version
download_version() {
    version=$1
    url="https://pypi.io/packages/source/o/open-cravat/open-cravat-${version}.tar.gz"
    curl -sL "$url" | tar xz
}

# Download both versions
download_version "2.8.0"
download_version "2.9.0"

# Compare setup.py files if they exist
if [ -f "open-cravat-2.8.0/setup.py" ] && [ -f "open-cravat-2.9.0/setup.py" ]; then
    echo "Differences in setup.py:"
    diff -u "open-cravat-2.8.0/setup.py" "open-cravat-2.9.0/setup.py" | grep "^[+-]" | grep -v "^[+-][+-][+-]"
fi

# Compare requirements.txt files if they exist
if [ -f "open-cravat-2.8.0/requirements.txt" ] && [ -f "open-cravat-2.9.0/requirements.txt" ]; then
    echo "Differences in requirements.txt:"
    diff -u "open-cravat-2.8.0/requirements.txt" "open-cravat-2.9.0/requirements.txt" | grep "^[+-]" | grep -v "^[+-][+-][+-]"
fi

# Clean up
rm -rf "open-cravat-2.8.0" "open-cravat-2.9.0"

This script will help identify any changes in dependencies between the two versions.

🧰 Tools

🪛 yamllint

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

(syntax)

---

10-10: SHA256 checksum update looks appropriate.

The SHA256 checksum has been updated, which is expected when changing to a new version of the package. However, it's important to verify that this new checksum is correct for the 2.9.0 source package.

To verify the checksum, you can run the following script:

---

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.

[BiocondaBot]

No artifacts found on the most recent builds. Either the builds failed, the artifacts have been removed due to age, or the recipe was blacklisted/skipped.

[BiocondaBot]

No artifacts found on the most recent builds. Either the builds failed, the artifacts have been removed due to age, or the recipe was blacklisted/skipped.