Update unassigner to 1.0.2

[BiocondaBot]

Update unassigner: 1.0.0 → 1.0.2

Info	Link or Description
Recipe	recipes/unassigner (click to view/edit other files)
Summary	Type strain identification for 16S reads
Home	https://github.com/PennChopMicrobiomeProgram/unassigner
Releases	https://pypi.org/pypi/unassigner/json
Recipe Maintainer(s)	@Ulthran

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request involves an update to the meta.yaml file for the "unassigner" package. The primary changes include an increment in the version number from "1.0.0" to "1.0.2" and an update to the SHA256 checksum for the source tarball. No other sections of the file, such as package metadata, build instructions, requirements, test commands, or descriptive information, were altered. The modifications are limited to the version and checksum, maintaining the overall structure and content of the meta.yaml file.

Possibly related PRs

• Update bactopia-py to 1.2.0 #51154: Updates to the meta.yaml file for bactopia-py to change the version and SHA256 checksum.
• Update peaks2utr to 1.3.3 #51170: Modifications to the meta.yaml file for peaks2utr to update the version and SHA256 checksum.
• Update bactopia-py to 1.2.1 #51226: Another update to the meta.yaml file for bactopia-py, changing the version and SHA256 checksum.
• Update viroconstrictor to 1.4.6 #51247: Changes made to the meta.yaml file for viroconstrictor, updating the version and SHA256 checksum.
• Update metabolights-utils to 1.1.11 #51352: The meta.yaml file for metabolights-utils was updated to change the version and SHA256 checksum.
• Update metabolights-utils to 1.1.12 #51383: A subsequent update to the meta.yaml file for metabolights-utils, reflecting changes to the version and SHA256 checksum.
• Update metabolights-utils to 1.2.1 #51403: Further updates to the meta.yaml file for metabolights-utils, changing the version and SHA256 checksum again.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 6b9962d and 59f20e2.

📒 Files selected for processing (1)

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

🧰 Additional context used

🪛 yamllint

recipes/unassigner/meta.yaml

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

(syntax)

🔇 Additional comments (3)

recipes/unassigner/meta.yaml (3)

2-2: Version update looks good.

The version has been correctly updated from "1.0.0" to "1.0.2", which is consistent with the PR objectives for this automated version bump.

---

1-46: File consistency verified.

I've reviewed the entire file, and all other sections (build, requirements, test, about, etc.) remain unchanged and are consistent with the version update. This is expected for a minor version bump.

Key points:

1. The build number is correctly set to 0 for the new version.
2. Package structure, dependencies, and metadata remain the same.

This consistency aligns with the automated nature of this version bump.

🧰 Tools

🪛 yamllint

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

(syntax)

---

10-10: SHA256 checksum has been updated.

The SHA256 checksum has been updated, which is expected when updating to a new version of the package. However, it's important to verify that this checksum is correct for the new version of the package.

To verify the checksum, you can run the following command:

---

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.