Update kalamari to 5.7.1

[BiocondaBot]

Update kalamari: 5.7.0 → 5.7.1

Info	Link or Description
Recipe	recipes/kalamari (click to view/edit other files)
Summary	A curated database of completed assemblies with taxonomy IDs
Home	https://github.com/lskatz/kalamari
Releases	https://github.com/lskatz/Kalamari/tags
Recipe Maintainer(s)	@lskatz, @rpetit3
Author	@lskatz

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request involves an update to the meta.yaml file for the "Kalamari" package. The version number has been changed from "5.7.0" to "5.7.1". In addition, the SHA256 checksum for the source tarball has been updated from d8d67bde9e4bbff75ae63c705f6c2ecdc6e2a378f71318744fc24f8420b78e68 to 41a70037424da3658e6c92e3faca335d4cf02301fc74a5b5b27cd2611aef5681. No other modifications to the structure or content of the meta.yaml file have been made.

Possibly related PRs

• Update savana to 1.2.2 #51103: Updates the version and SHA256 checksum in the meta.yaml file for the savana package.
• Update sizemeup to 1.2.3 #51114: Involves updating the version and SHA256 checksum in the meta.yaml file for the sizemeup package.
• Update peaks2utr to 1.3.3 #51170: Updates the meta.yaml file for the peaks2utr package with a new version and SHA256 checksum.
• Update libcifpp to 7.0.7 #51196: Similar updates to the version and SHA256 checksum in the meta.yaml file for the libcifpp package.

Suggested reviewers

• rpetit3

---

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/kalamari/meta.yaml (1)

Line range hint 1-54: LGTM: Changes are consistent with a minor version update.

The updates to the version number and SHA256 checksum are the only necessary changes for this minor version update. All other fields in the meta.yaml file remain appropriately unchanged.

As a minor suggestion for improvement:

Consider adding a build section to pin the minimum version of Python required, if applicable. This can help ensure compatibility and prevent potential issues with older Python versions. For example:

build:
  number: 0
  noarch: python
  script: {{ PYTHON }} -m pip install . -vv

This change is not strictly necessary for this update but could be beneficial for future maintenance.

🧰 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 454f325 and f3e25a8.

📒 Files selected for processing (1)

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

🧰 Additional context used

🔇 Additional comments (2)

recipes/kalamari/meta.yaml (2)

2-2: LGTM: Version number updated correctly.

The version number has been properly updated from "5.7.0" to "5.7.1", which aligns with the PR objectives.

---

10-10: Verify the updated SHA256 checksum.

The SHA256 checksum has been updated, which is expected with a new version. However, it's crucial to ensure that this checksum corresponds to the correct source tarball for version 5.7.1.

Please run the following script to verify the SHA256 checksum: