Update meta.yaml

[BioOmics]

Describe your pull request here

---

Please read the guidelines for Bioconda recipes before opening a pull request (PR).

General instructions

• If this PR adds or updates a recipe, use "Add" or "Update" appropriately as the first word in its title.
• New recipes not directly relevant to the biological sciences need to be submitted to the conda-forge channel instead of Bioconda.
• PRs require reviews prior to being merged. Once your PR is passing tests and ready to be merged, please issue the @BiocondaBot please add label command.
• Please post questions on Gitter or ping @bioconda/core in 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_exports section like this:

build:
  run_exports:
    - ...

with ... being one of:

Case	run_exports statement
semantic versioning	{{ pin_subpackage("myrecipe", max_pin="x") }}
semantic versioning (0.x.x)	{{ pin_subpackage("myrecipe", max_pin="x.x") }}
known breakage in minor versions	{{ pin_subpackage("myrecipe", max_pin="x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)
known breakage in patch versions	{{ pin_subpackage("myrecipe", max_pin="x.x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)
calendar versioning	{{ pin_subpackage("myrecipe", max_pin=None) }}

while replacing "myrecipe" with either name if a name|lower variable 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	Merge the master branch into a PR.
@BiocondaBot please add label	Add the please review & merge label.
@BiocondaBot please fetch artifacts	Post links to CI-built packages/containers. You can use this to test packages locally.

Note that the @BiocondaBot please merge command 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>.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request modifies the meta.yaml file for the iSeq package, specifically for version 1.1.0. The primary change involves the removal of a specific version constraint for the sra-tools dependency in the run requirements section. The line that previously specified sra-tools =2.11.0 has been changed to simply sra-tools, allowing for the use of any version of this dependency. Additionally, there is a minor formatting correction where the indentation of the - wget line has been adjusted for proper alignment with other dependencies. Overall, the structure of the meta.yaml file remains unchanged, with no modifications to the package name, version, source URL, SHA256 checksum, build specifications, test commands, or other metadata.

Possibly related PRs

• 2024.4 #50977: Updates to the meta.yaml file for the biobb_structure_checking package involve changes to versioning and SHA256 checksum, relating to dependency management.
• update Hsdecipher des #51023: Modifications in the hsdecipher package's meta.yaml include changes to the SHA256 checksum and command-line interface, involving the meta.yaml structure.
• [biobb_amber] update 5.0.0 #51430: The biobb_amber package's meta.yaml updates include version increments and dependency adjustments, similar to the changes made in the iSeq package.
• [biobb_analysis] update 5.0.0 #51431: The biobb_analysis package's meta.yaml updates involve version increments and dependency adjustments, aligning with the iSeq package's dependency management changes.
• [biobb_chemistry] update 5.0.0 #51435: Updates to the biobb_chemistry package's meta.yaml include version increments and dependency adjustments, reflecting similar dependency management changes as in the iSeq package.
• [biobb_cmip] update 5.0.0 #51453: The biobb_cmip package's meta.yaml updates involve version increments and dependency adjustments, related to the changes made in the iSeq package.

Suggested labels

please review & merge

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between bb85acb and b0fd4c1.

📒 Files selected for processing (1)

• recipes/iseq/meta.yaml (1 hunks)

🧰 Additional context used

🔇 Additional comments (2)

recipes/iseq/meta.yaml (2)

Line range hint 1-42: Overall recipe quality is good

Apart from the sra-tools version constraint issue, the rest of the recipe adheres to conda packaging best practices:

1. It uses jinja2 templating for version and name.
2. It includes a run_exports section for proper version pinning.
3. Test commands are provided to verify the installation.
4. Metadata like license, summary, and maintainer information is included.

The recipe structure and content are well-maintained. Once the sra-tools version constraint is addressed, this recipe should be ready for use.

---

26-26: 🛠️ Refactor suggestion

Consider using a flexible version constraint for sra-tools

The removal of the specific version constraint for sra-tools might lead to potential compatibility issues and inconsistent behavior across different environments. While this change allows for greater flexibility, it also introduces risks:

1. Future versions of sra-tools might introduce breaking changes that could affect the functionality of iSeq.
2. It becomes harder to ensure reproducibility of environments using this package.
3. This change is inconsistent with the version management of other dependencies in the recipe.

To ensure this change doesn't introduce unforeseen issues:

Consider using a more flexible version constraint instead of removing it entirely. For example:

- sra-tools >=2.11.0,<3

This ensures compatibility with versions 2.11.0 and above, but below 3.0.0, which should provide both flexibility and some level of version control.

---

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?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.