Update blaze2 to 2.5.0

[BiocondaBot]

Update blaze2: 2.4.0 → 2.5.0

Info	Link or Description
Recipe	recipes/blaze2 (click to view/edit other files)
Summary	Barcode identification from (Nanopore) Long reads for AnalyZing single-cell gene Expression.
Home	https://github.com/shimlab/BLAZE
Releases	https://github.com/shimlab/BLAZE/tags
Author	@shimlab

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates the meta.yaml file for the BLAZE2 package, incrementing the version from "2.4.0" to "2.5.0". The source URL has been changed to reflect the new version's tarball, and the SHA-256 checksum has been updated to match the new source package.

Changes

File Path	Change Summary
recipes/blaze2/meta.yaml	- Version updated from "2.4.0" to "2.5.0" - Source URL updated to v2.5.0.tar.gz - SHA256 checksum updated from b4487873d1f4ae389feed54aa7d862ff3addc458c387d6fd0e3c9550c0a2037d to f47175997742562add1deb9524e468b6709e40c92f74165a1a0fe1897b2919fc

Possibly related PRs

• Update vsearch to 2.29.0 #50975: Updates the meta.yaml file for the vsearch package, involving a version increment and SHA256 checksum update.
• Update peaks2utr to 1.3.2 #50979: Involves an update to the meta.yaml file for the peaks2utr package, reflecting a version change and SHA256 checksum update.
• Update open-cravat to 2.9.0 #50999: Updates the meta.yaml file for the open-cravat package, including a version increment and SHA256 checksum modification.
• Update straglr to 1.5.2 #51000: Updates the meta.yaml file for the straglr package, involving a version change and SHA256 checksum update.
• Update gempipe to 1.35.3 #51008: Reflects an update to the meta.yaml file for the gempipe package, including a version increment and SHA256 checksum update.
• Update pybiolib to 1.2.181 #51015: Updates the meta.yaml file for the pybiolib package, involving a version change and SHA256 checksum update.
• Update trgt to 1.2.0 #51017: Updates the meta.yaml file for the trgt package, including a version increment and SHA256 checksum update.
• Update ont-modkit to 0.4.1 #51025: Involves an update to the meta.yaml file for the ont-modkit package, reflecting a version change and SHA256 checksum update.
• Update parsnp to 2.0.6 #51028: Updates the meta.yaml file for the parsnp package, including a version increment and SHA256 checksum modification.
• Update gxf2bed to 0.2.3 #51029: Reflects an update to the meta.yaml file for the gxf2bed package, involving a version change and SHA256 checksum update.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between f0b880c and 6d4b39d.

📒 Files selected for processing (1)

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

🔇 Additional comments (3)

recipes/blaze2/meta.yaml (3)

2-2: Version update looks good.

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

---

10-10: SHA256 checksum update looks correct.

The SHA256 checksum has been updated, which is expected due to the new version. However, it's important to verify that this checksum corresponds to the correct tarball.

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

#!/bin/bash
# Description: Verify the SHA256 checksum of the source tarball

# Download the tarball
curl -L https://github.com/shimlab/BLAZE/archive/refs/tags/v2.5.0.tar.gz -o blaze2.tar.gz

# Calculate and compare the SHA256 checksum
echo "f47175997742562add1deb9524e468b6709e40c92f74165a1a0fe1897b2919fc blaze2.tar.gz" | sha256sum -c -

# Clean up
rm blaze2.tar.gz

---

Line range hint 1-55: Overall package structure looks good.

The source URL is correctly templated to use the new version, and the build number is appropriately set to 0 for the new version. Dependencies and other metadata remain unchanged, which suggests compatibility with the previous environment.

It might be worth double-checking if there are any new dependencies or changes in the minimum required versions for the new BLAZE2 release. You can verify this by checking the release notes or the project's documentation for version 2.5.0.

To help with this, you can run the following script to check for any mention of new dependencies or version changes in the project's README or CHANGELOG:

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