coderabbitai[bot]
commented
4 days ago 📝 Walkthrough
📝 Walkthrough
📝 Walkthrough
📝 Walkthrough
📝 Walkthrough
## Walkthrough The changes in this pull request involve updates to the `meta.yaml` file for the `vclust` package. The package version has been incremented from "1.2.7" to "1.2.8". Specific platform identifiers have replaced generic system identifiers, now including `manylinux2014_x86_64`, `manylinux2014_aarch64`, `macosx_10_9_x86_64`, and `macosx_11_0_arm64`. New `site` variables have been introduced, providing URLs for the wheel files for each platform, and the SHA256 checksums have been updated accordingly. The build process has shifted from manual directory creation and file copying to using a pip install command sourced from the new `site` URLs. Additionally, the command for running the tool has changed from `vclust.py` to `vclust`, indicating a modification in the invocation method. ## Possibly related PRs - **#50007**: This PR is directly related as it also modifies the `meta.yaml` file for the `vclust` package, updating the version and system specifications, similar to the changes made in the main PR. ## Suggested labels `autobump`, `new version` ## Suggested reviewers - martin-gThank 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?
agudys
Update vclust to 1.2.8
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 arun_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.
@BiocondaBot please mergecommand is now depreciated. Please just squash and merge instead. Also, the bot watches for comments from non-members that include `@bioconda/