-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update nextclade to 3.9.1 #51763
Update nextclade to 3.9.1 #51763
Conversation
@BiocondaBot please add label |
📝 WalkthroughWalkthroughThe pull request includes an update to the
Each platform's checksum has been updated to reflect the new version, ensuring that the integrity of the package can be verified. No other modifications to the structure or content of the Possibly related PRs
Suggested labels
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🔇 Additional comments (3)recipes/nextclade/meta.yaml (3)
Version update matches the PR objective and follows semantic versioning. Line range hint The recipe follows Bioconda best practices:
🧰 Tools🪛 yamllint[error] 1-1: syntax error: found character '%' that cannot start any token (syntax)
Let's verify the checksums match the official Nextclade 3.9.1 release artifacts. 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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Update nextclade: 3.9.0 → 3.9.1.
@BiocondaBot please add label
@BiocondaBot please fetch artifacts
Note: this pull request is submitted automatically, triggered by a release in nextstrain/nextclade repo. If you want to get in touch, please ping recipe maintainers and/or someone from
@nextstrain/core
team.