Update oakvar to 2.11.24

[BiocondaBot]

Update oakvar: 2.11.21 → 2.11.24

Info	Link or Description
Recipe	recipes/oakvar (click to view/edit other files)
Summary	OakVar - Genomic Variant Analysis Platform
Home	https://github.com/rkimoakbioinformatics/oakvar
Releases	https://pypi.org/pypi/oakvar/json
Recipe Maintainer(s)	@rkimoakbioinformatics

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

📝 Walkthrough

📝 Walkthrough

Walkthrough

The pull request involves an update to the meta.yaml file for the OakVar package. The version number has been changed from "2.11.21" to "2.11.24". Additionally, the SHA256 checksum has been updated from "e9a479ada8d64d8c425ebeb9ad217f6a41583ae7a41e4ee1df52851cd71d2d8a" to "72b3f427b66b2bea8a7b36038f6164e3623b6b6d88c945db659fc06c4d6bed3e". These modifications ensure that the updated version and its corresponding checksum are accurately represented for the build and installation processes of the OakVar software.

Possibly related PRs

• Update oakvar to 2.11.11 #51279: Updates the meta.yaml file for the OakVar package, changing the version from "2.11.10" to "2.11.11" and updating the SHA256 checksum.
• Update oakvar to 2.11.12 #51387: Updates the meta.yaml file for the OakVar package, changing the version from "2.11.11" to "2.11.12" and updating the SHA256 checksum.
• Update oakvar to 2.11.14 #51409: Updates the meta.yaml file for the OakVar package, changing the version from "2.11.12" to "2.11.13" and updating the SHA256 checksum.
• Update oakvar to 2.11.21 #51512: Updates the meta.yaml file for the OakVar package, changing the version from "2.11.14" to "2.11.20" and updating the SHA256 checksum.
• Update clinvar-this to 0.18.3 #51560: Updates the meta.yaml file for the OakVar package, changing the version from "2.11.20" to "2.11.21" and updating the SHA256 checksum.

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

recipes/oakvar/meta.yaml (1)

Line range hint 59-63: Consider enhancing test coverage.

While the current tests are sufficient for a version bump, consider adding more comprehensive tests such as:

• Version check command (ov --version)
• Basic module functionality tests

🧰 Tools

🪛 yamllint

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

(syntax)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between d792d8e and a55299d.

📒 Files selected for processing (1)

• recipes/oakvar/meta.yaml (1 hunks)

🔇 Additional comments (3)

recipes/oakvar/meta.yaml (3)

Line range hint 14-21: LGTM! Build configuration follows best practices.

The build configuration is well-structured with:

• Appropriate build number reset
• Correct noarch Python specification
• Proper pip installation flags
• Appropriate run_exports pinning

🧰 Tools

🪛 yamllint

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

(syntax)

---

Line range hint 23-57: LGTM! Dependencies are well-defined.

The package has a comprehensive and well-structured dependency list with appropriate version constraints where needed.

🧰 Tools

🪛 yamllint

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

(syntax)

---

2-3: Verify SHA256 checksum against PyPI package.

The version update looks correct. Let's verify the SHA256 checksum matches the PyPI package.