coderabbitai[bot]
commented
1 day ago 📝 Walkthrough
## Walkthrough This pull request introduces modifications to the `meta.yaml` files for multiple `hmftools` packages. The changes include updates to version numbers and build numbers across the packages. Specifically, the `hmftools-purple` package's build number is increased from 2 to 3, and its OpenJDK requirement is revised to a version range of `>=8,<=21`. The `hmftools-sage` package sees its version updated to "4.0_beta.3" and its build number incremented from 3 to 4, with a similar OpenJDK requirement adjustment. The `hmftools-sigs` package's build number is updated from 0 to 1, along with a change in the OpenJDK requirement to `>=8,<=21`. Lastly, the `hmftools-virus-interpreter` package has its version set to "3.7_beta," its build number increased from 0 to 1, and the OpenJDK requirement adjusted to the same version range. The source URLs and other metadata remain unchanged across these packages. ## Possibly related PRs - **#51294**: Updates the `hmftools-purple` package's `meta.yaml` file, modifying the `openjdk` requirement to `>=8,<=21`. - **#51698**: Similar to the main PR, this PR updates the `hmftools-purple` package's `meta.yaml` file to specify the `openjdk` requirement as `>=8,<=21`. - **#51800**: Modifies the `hmftools-purple` package's `meta.yaml` file, changing the `openjdk` requirement to `>=8,<=21`. - **#52122**: Updates the `hmftools-redux` package's `meta.yaml` file to set the `openjdk` requirement to `>=8,<=21`. ## Suggested labels `please review & merge` ## Suggested reviewers - martin-g - mencianThank 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?
luan-n-nguyen
bgruening
Describe your pull request here
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/