Xiangyang1984 patch 20

[Xiangyang1984]

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 involves updates to the meta.yaml file for the pneumo-typer package. The version number has been incremented from "1.0.2" to "1.0.3", and the SHA256 checksum has been updated to reflect a new source package. The build number has been modified from 1 to 0. Additionally, the requirements section has been updated to specify minimum version requirements for dependencies: perl-gd is now required to be version >=2.74, and perl-svg is required to be version >=2.87. No other changes to the structure or content of the file were made.

Possibly related PRs

• add pneumo-typer recipes #51358: This PR updates the meta.yaml file for the pneumo-typer package, which is directly related to the main PR that also modifies the meta.yaml for the same package, including version and SHA256 updates.
• Xiangyang1984 patch 10 #51382: Similar to the main PR, this PR also updates the meta.yaml file for the pneumo-typer package, including changes to the version number and SHA256 checksum, indicating a direct relationship.

Suggested labels

please review & merge

Suggested reviewers

• bioconda-bot

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 5026036 and db5f3e7.

📒 Files selected for processing (1)

• recipes/pneumo-typer/meta.yaml (3 hunks)

🧰 Additional context used

🔇 Additional comments (5)

recipes/pneumo-typer/meta.yaml (5)

2-2: LGTM: Version update looks good.

The version has been correctly updated from 1.0.2 to 1.0.3, which is consistent with the PR objectives.

---

15-15: LGTM: Build number reset is correct.

The build number has been appropriately reset to 0 for the new version. This follows the best practices for Conda package versioning.

---

Line range hint 1-54: Overall, the changes look good and follow best practices.

The updates to the pneumo-typer package recipe are consistent with a minor version update. The version number, SHA256 checksum, build number, and dependency versions have been appropriately updated. Please ensure that all suggested verifications are performed to guarantee the correctness and necessity of these changes.

🧰 Tools

🪛 yamllint

[error] 22-22: trailing spaces

(trailing-spaces)

---

25-27: Verify the necessity of the new version constraints for perl-gd and perl-svg.

The minimum version requirements for perl-gd and perl-svg have been updated:

• perl-gd now requires version 2.74 or higher
• perl-svg now requires version 2.87 or higher

These changes improve dependency management by ensuring compatibility with specific versions. However, please verify that these constraints are necessary for the new version of pneumo-typer and don't overly restrict users.

To verify the necessity of these version constraints, you can check the changelog or release notes of pneumo-typer v1.0.3 for any mentions of required updates to these dependencies. Additionally, you can run the following command to check the availability of these versions in the bioconda channel:

#!/bin/bash
# Description: Check availability of specified perl-gd and perl-svg versions in bioconda

conda search -c bioconda perl-gd>=2.74
conda search -c bioconda perl-svg>=2.87

---

4-4: Verify the updated SHA256 checksum.

The SHA256 checksum has been updated, which is expected with a new version. Please ensure that this checksum correctly corresponds to the new source package.

To verify the checksum, you can run the following command:

---

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.