Update auspice to 2.59.0

[victorlin]

• Update auspice to new version
• Update list of supported Node.js versions

---

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 an update to the meta.yaml file for the auspice package. The version number has been changed from "2.58.0" to "2.59.0," and the SHA256 checksum has been updated to reflect the new version. Additionally, the requirements for Node.js in both the build and run sections have been modified to include version 22, expanding the previously supported versions of 16., 18., and 20.*. No other modifications to the structure or content of the file have been made.

Possibly related PRs

• Update Hsdecipher #51093: This PR updates the version and SHA256 checksum in the meta.yaml file for the HSDecipher package, similar to the version and checksum updates in the main PR for the auspice package.
• update Hsdecipher des #51023: This PR updates the SHA256 checksum in the meta.yaml file for the hsdecipher package, which is relevant as it involves a checksum update similar to the one in the main PR.

Suggested labels

please review & merge

Suggested reviewers

• bgruening

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 941148a and 950295a.

📒 Files selected for processing (1)

• recipes/auspice/meta.yaml (3 hunks)

🧰 Additional context used

🪛 yamllint

recipes/auspice/meta.yaml

[error] 1-1: syntax error: found character '%' that cannot start any token

(syntax)

🔇 Additional comments (4)

recipes/auspice/meta.yaml (4)

Line range hint 12-15: LGTM! Appropriate version pinning strategy

The run_exports configuration with max_pin="x.x" correctly ensures compatibility with minor version updates, following semantic versioning principles.

---

Line range hint 1-58: Overall changes look good

The recipe update follows Bioconda guidelines with appropriate:

• Version bump
• Checksum update
• Build number reset
• Version pinning strategy
• Dependency management

Note: The yamllint error can be ignored as it's a false positive for Jinja2 templates.

---

23-23: Verify Node.js 22.x compatibility

While adding Node.js 22.* support expands compatibility, please verify:

1. That auspice 2.59.0 has been tested with Node.js 22
2. That Node.js 22 is stable enough for production use

#!/bin/bash
# Description: Check if auspice explicitly documents Node.js version support

# Search for Node.js version requirements in package.json
curl -sL https://registry.npmjs.org/auspice/-/auspice-2.59.0.tgz | \
  tar xzf - -O package/package.json | \
  jq -r '.engines.node'

# Look for any Node.js version related information in README
curl -sL https://registry.npmjs.org/auspice/-/auspice-2.59.0.tgz | \
  tar xzf - -O package/README.md | \
  grep -i "node"

Also applies to: 30-30

---

1-1: Verify package integrity

Let's verify that the SHA256 checksum matches the published NPM package.

Also applies to: 9-10

🧰 Tools

🪛 yamllint

[error] 1-1: syntax error: found character '%' that cannot start any token

(syntax)

---

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.