coderabbitai[bot]
commented
3 days ago 📝 Walkthrough
📝 Walkthrough
## Walkthrough The pull request modifies the `meta.yaml` file for the `isoseq` package. It updates the package version from `4.0.0` to `4.2.0` and changes the SHA256 checksum to reflect this new version. Additionally, the `build` section of the `meta.yaml` file is enhanced with two new entries: `binary_relocation` is set to `False`, and a `run_exports` field is added. The `run_exports` field specifies a dependency on the `isoseq` subpackage with a maximum pinning of `x.x`. These changes indicate a version upgrade and adjustments to the build configuration, particularly concerning binary relocation and runtime dependencies. ## Possibly related PRs - #49857: Updates the `meta.yaml` file for the `spec2vec` package, including a new `run_exports` section similar to the changes made in the `isoseq` package. - #50977: Updates the `meta.yaml` file for the `biobb_structure_checking` package, including a version update and SHA256 checksum change, aligning with the changes in the `isoseq` PR. - #51372: Updates the `meta.yaml` file for the `resistify` package, reflecting a version increment and SHA256 checksum update, similar to the changes in the `isoseq` PR. - #51486: Updates the `meta.yaml` file for the `neat` package, including a version update and SHA256 checksum change, consistent with the updates in the `isoseq` PR. - #51583: Updates the `meta.yaml` file for the `iSeq` package, including a version update and SHA256 checksum change, paralleling the changes in the `isoseq` PR. - #51584: Also updates the `meta.yaml` file for the `iSeq` package, with similar changes to version and SHA256 checksum, indicating a related update process. - #51638: Updates the `meta.yaml` file for the `neat` package, reflecting a version increment and SHA256 checksum update, consistent with the changes in the `isoseq` 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?
jmattick
BiocondaBot
aliciaaevans
Update isoseq version 4.2.0
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/