Update cmat to 3.3.0

[BiocondaBot]

Update cmat: 3.2.2 → 3.3.0

Info	Link or Description
Recipe	recipes/cmat (click to view/edit other files)
Summary	ClinVar Mapping and Annotation Toolkit
Home	https://github.com/EBIvariation/CMAT
Releases	https://github.com/EBIvariation/CMAT/tags
Recipe Maintainer(s)	@apriltuesday
Author	@EBIvariation

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request involves an update to the meta.yaml file for the cmat package. The primary changes include an increment of the version number from "3.2.2" to "3.3.0" and an update of the SHA256 checksum to reflect the new version. The previous checksum was 63b052052e6c3809e2d55835bfbe1dbd5ee312d6ef12906b25e5c67816fa6186, which has been changed to d39137937c2827b401fe7ca10ccaaf4f8dbbac049e7ea5b86ded6713bf1efdba. There are no additional modifications to other sections such as requirements, build, test, about, or extra in this update.

Possibly related PRs

• Update picard to 3.3.0 #51282: The picard package's version was updated from "3.2.0" to "3.3.0" and the SHA256 checksum was changed, similar to the version and checksum updates in the main PR for the cmat package.
• Update picard-slim to 3.3.0 #51286: The picard-slim package's version was also updated from "3.2.0" to "3.3.0" with a corresponding SHA256 checksum change, paralleling the changes made in the main PR for the cmat package.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 74bb24f and 90d7644.

📒 Files selected for processing (1)

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

🧰 Additional context used

🔇 Additional comments (3)

recipes/cmat/meta.yaml (3)

2-2: Version update looks good.

The version has been correctly updated to 3.3.0, which aligns with the PR objective.

---

Line range hint 1-71: Verify dependencies and check for new features.

While the version update and checksum change look good, please consider the following:

1. Verify if any dependencies need to be updated for version 3.3.0.
2. Check if there are any new features or changes in version 3.3.0 that might require updates to the recipe (e.g., new dependencies, build steps, or test commands).

It's a good practice to review the changelog or release notes for version 3.3.0 to ensure all necessary changes are reflected in the recipe.

To assist with this verification, you can run the following script to check for a changelog or release notes:

✅ Verification successful

Dependencies and new features verified.

No changes to dependencies are required based on the release notes for version 3.3.0. The recipe accurately reflects the necessary dependencies, and there are no new features that necessitate updates to the recipe.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for changelog or release notes for cmat 3.3.0

# Check for CHANGELOG file
if rg -i "changelog" --files-with-matches; then
    echo "Changelog found. Please review for any dependency or feature changes."
else
    echo "No changelog found in the repository."
fi

# Check for release notes on GitHub
echo "Checking GitHub release notes..."
gh release view v3.3.0 -R EBIvariation/CMAT

Length of output: 1170

🧰 Tools

🪛 yamllint

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

(syntax)

---

10-10: Verify the SHA256 checksum.

The SHA256 checksum has been updated. Let's verify if this checksum is correct for the new version 3.3.0 of the cmat package.

Run the following script to verify 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.