coderabbitai[bot]
commented
3 days ago 📝 Walkthrough
## Walkthrough The pull request modifies the `meta.yaml` file for the `pbskera` package. The primary changes include updating the package version from "1.2.0" to "1.3.0" and changing the SHA256 checksum from "0385ab4d67377cd6ed596eccd5df973c03d78561db639d84f9ff557332f745be" to "1784969ff410da7d53b1bd0432f3d4f825524e5b99bfa7956aa7dab33a28cedc". These updates are the only alterations made to the file, with no additional structural or functional changes. The overall format of the `meta.yaml` file remains consistent with its previous version. ## Possibly related PRs - #51027: Updates the version and SHA256 checksum in the `meta.yaml` file for the `pbskera` package. - #51142: Updates the version and SHA256 checksum in the `meta.yaml` file for the `hmftools-bam-tools` package. - #51170: Updates the version and SHA256 checksum in the `meta.yaml` file for the `peaks2utr` package. - #51430: Updates the version and SHA256 checksum in the `meta.yaml` file for the `biobb_amber` package. - #51435: Updates the version and SHA256 checksum in the `meta.yaml` file for the `biobb_chemistry` package. - #51528: Updates the version and SHA256 checksum in the `meta.yaml` file for the `biobb_cp2k` package. - #51649: Updates the version and SHA256 checksum in the `meta.yaml` file for the `biobb_amber` package. ## Suggested labels `autobump`, `new version`📜 Recent review details
**Configuration used: CodeRabbit UI** **Review profile: CHILL**📥 Commits
Files that changed from the base of the PR and between a83862eff5904e5bc34fd143ebe35b7b141b0008 and 0a04d4a82abd0520da186e255748c9f1c7cb88e1.📒 Files selected for processing (1)
* recipes/pbskera/meta.yaml (2 hunks)🔇 Additional comments (3)
recipes/pbskera/meta.yaml (3)
`2-2`: **LGTM: Version update follows semantic versioning** The version update to 1.3.0 is properly formatted and consistent with the PR objectives. --- Line range hint `26-33`: **LGTM: Package configuration follows best practices** The package configuration is well structured with: - Proper version pinning using run_exports - Appropriate noarch flag - Basic test command - Well-documented skip-lints --- `3-3`: **Verify SHA256 checksum against the official release** Let's verify that the SHA256 checksum matches the official release artifact.
jmattick
BiocondaBot
aliciaaevans
Update pbskera version 1.3.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/