Update centrifuge to 1.0.4.2

[BiocondaBot]

Update centrifuge: 1.0.4.1 → 1.0.4.2

Info	Link or Description
Recipe	recipes/centrifuge (click to view/edit other files)
Summary	Classifier for metagenomic sequences. Supports classifier scripts
Home	https://github.com/DaehwanKimLab/centrifuge
Releases	https://github.com/DaehwanKimLab/centrifuge/tags
Author	@DaehwanKimLab

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces modifications to the meta.yaml file for the centrifuge package. Key changes include an increment in the version number from 1.0.4.1 to 1.0.4.2, indicating a new release. Additionally, the build number has been reset from 2 to 0, which typically signifies a fresh build cycle. The SHA256 checksum has been updated from 638cc6701688bfdf81173d65fa95332139e11b215b2d25c030f8ae873c34e5cc to db142790522a72971c7deda7d22e1f29fce54dbf23afc2e40def9f5a764f4c99, reflecting a change in the source archive associated with the package. No other changes to the logic, error handling, or control flow are present in this update.

Possibly related PRs

• Update merquryfk to 1.1.0 #51308: The changes in this PR involve updating the version and SHA256 checksum in the meta.yaml file for the merquryfk package, similar to the version and checksum updates in the main PR for the centrifuge package.
• Update unassigner to 1.0.2 #51454: This PR updates the version and SHA256 checksum in the meta.yaml file for the unassigner package, which aligns with the version and checksum updates made in the main PR for the centrifuge package.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 8dd05cc and dc29a48.

📒 Files selected for processing (1)

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

🧰 Additional context used

🔇 Additional comments (4)

recipes/centrifuge/meta.yaml (4)

2-2: Version update looks good.

The version has been correctly updated from 1.0.4.1 to 1.0.4.2, which aligns with the PR objectives.

---

9-9: Build number reset is correct.

The build number has been appropriately reset to 0 for the new version, which is in line with Conda packaging best practices.

---

16-16: SHA256 checksum updated, verification recommended.

The SHA256 checksum has been updated to reflect the new version. This change is necessary and expected.

To ensure the integrity and authenticity of the package, please verify the SHA256 checksum against the official release:

Please ensure that the calculated SHA256 matches the one in the meta.yaml file.

---

Line range hint 1-54: Verify recipe completeness and accuracy.

While the version update, build number reset, and SHA256 change look good, please ensure that:

1. All build and run requirements are still valid for version 1.0.4.2.
2. The linux-aarch64 patch file (centrifuge-linux-aarch64.patch) is still applicable and necessary for the new version.
3. The test command centrifuge --help is still appropriate for verifying the installation.
4. The license information and summary are up-to-date.

To assist with this verification, you can run the following commands:

Please review the output and make any necessary adjustments to the recipe.

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