Update augur to 26.2.0 #52251
Update augur to 26.2.0 #52251
Conversation
📝 WalkthroughWalkthroughThe pull request introduces updates to the Possibly related PRs
Suggested labels
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🧰 Additional context used🪛 yamllintrecipes/augur/meta.yaml[error] 1-1: syntax error: found character '%' that cannot start any token (syntax) 🔇 Additional comments (4)recipes/augur/meta.yaml (4)Line range hint The build configuration is well-structured with:
🧰 Tools🪛 yamllint[error] 1-1: syntax error: found character '%' that cannot start any token (syntax) Line range hint The configuration includes:
🧰 Tools🪛 yamllint[error] 1-1: syntax error: found character '%' that cannot start any token (syntax)
The constraint change from ✅ Verification successfulPandas 2.x compatibility is verified The release notes for augur 26.2.0 explicitly state: "This is the first version to officially support Python 3.12 and Pandas v2." This confirms that the package maintainers have tested and verified compatibility with pandas 2.x. 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Check augur's release notes and issues for pandas 2.x compatibility
gh api repos/nextstrain/augur/releases/tags/26.2.0 --jq .body | grep -i pandas
rg -i "pandas.*2\." -g "!node_modules" -g "!build" -g "!dist"
Length of output: 8042
Let's confirm the version and SHA256 checksum match the official release. 🧰 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? 🪧 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 (
|
Bump version and update dependencies
Please read the guidelines for Bioconda recipes before opening a pull request (PR).
General instructions
@BiocondaBot please add labelcommand.@bioconda/corein a comment.Instructions for avoiding API, ABI, and CLI breakage issues
Conda is able to record and lock (a.k.a. pin) dependency versions used at build time of other recipes.
This way, one can avoid that expectations of a downstream recipe with regards to API, ABI, or CLI are violated by later changes in the recipe.
If not already present in the meta.yaml, make sure to specify
run_exports(see here for the rationale and comprehensive explanation).Add a
run_exportssection like this:with
...being one of:{{ pin_subpackage("myrecipe", max_pin="x") }}{{ pin_subpackage("myrecipe", max_pin="x.x") }}{{ pin_subpackage("myrecipe", max_pin="x.x") }}(in such a case, please add a note that shortly mentions your evidence for that){{ pin_subpackage("myrecipe", max_pin="x.x.x") }}(in such a case, please add a note that shortly mentions your evidence for that){{ pin_subpackage("myrecipe", max_pin=None) }}while replacing
"myrecipe"with eithernameif aname|lowervariable is defined in your recipe or with the lowercase name of the package in quotes.Bot commands for PR management
Please use the following BiocondaBot commands:
Everyone has access to the following BiocondaBot commands, which can be given in a comment:
@BiocondaBot please update@BiocondaBot please add labelplease review & mergelabel.@BiocondaBot please fetch artifactsYou can use this to test packages locally.
Note that the
@BiocondaBot please mergecommand is now depreciated. Please just squash and merge instead.Also, the bot watches for comments from non-members that include
@bioconda/<team>and will automatically re-post them to notify the addressed<team>.