Update buscolite to 24.11.3

[BiocondaBot]

Update buscolite: 23.10.26 → 24.11.3

Info	Link or Description
Recipe	recipes/buscolite (click to view/edit other files)
Summary	buscolite: busco analysis for gene predictions
Home	https://github.com/nextgenusfs/buscolite
Releases	https://pypi.org/pypi/buscolite/json
Recipe Maintainer(s)	@nextgenusfs

---

This pull request was automatically generated (see docs).

[coderabbitai]

Warning

Rate limit exceeded

@mencian has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 18 minutes and 30 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 60d3e9f and 6a09984.

📝 Walkthrough

📝 Walkthrough

Walkthrough

This pull request introduces changes to the meta.yaml file of the buscolite package. The primary modifications include an update to the version number, which has been changed from 23.10.26 to 24.11.3. Additionally, the SHA256 checksum for the source tarball has been updated to reflect the new version, changing from c641dc6c702fa198fd6fa661b756aedde4468ea591c8c64f8b8bd9c8a865b72d to f7ef8151b2dd16848ec8bf7e14658a81db3fbe7898e6377a2bb0553cf065f47b. No other changes were made to the structure or content of the meta.yaml file.

Possibly related PRs

• Update busco to v5.8.0 #51337: The changes in this PR involve updating the meta.yaml file for the busco package, which includes a version increment and SHA256 checksum update, similar to the changes made in the main PR for the buscolite package.

---

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: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 9f4b71f and 60d3e9f.

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

recipes/buscolite/meta.yaml (1)

10-10: Verify SHA256 checksum authenticity.

The SHA256 checksum has been updated as expected with the version change.

Let's verify the checksum matches the source tarball:

[coderabbitai]

💡 Codebase verification

Version update is incorrect - missing 'v' prefix

The version in meta.yaml should be "v24.11.3" to match the upstream release tag format. All releases in the repository use the 'v' prefix (v24.11.3, v24.7.29, v23.10.26, etc.).

🔗 Analysis chain

Version update looks correct.

The version update from 23.10.26 to 24.11.3 follows the expected date-based versioning pattern. The build number is correctly reset to 0 for the new version.

Let's verify the version exists in the upstream repository:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify the version tag exists in the upstream repository
gh release view 24.11.3 --repo nextgenusfs/buscolite

Length of output: 72

---

Script:

#!/bin/bash
# Let's check all available releases to see the correct version format
gh release list --repo nextgenusfs/buscolite --limit 10

Length of output: 307