Update iseq to 1.2.0

[BiocondaBot]

Update iseq: 1.1.0 → 1.2.0

Info	Link or Description
Recipe	recipes/iseq (click to view/edit other files)
Summary	iSeq is a Bash script that allows you to download sequencing data and metadata from GSA, SRA, ENA, and DDBJ databases
Home	https://github.com/BioOmics/iSeq
Releases
Recipe Maintainer(s)	@haoyu Chao haoyuchao@zju.edu.cn
Author	@BioOmics

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates the meta.yaml file for the iSeq package. The primary change is the increment of the version number from "1.1.0" to "1.2.0". Additionally, the SHA256 checksum for the source tarball has been modified from de0b9f1e06842a14f0a112023b989a38f6d422d860d44b19d3ec717d3c00bc34 to 9ddac60c63f774aac274de5a2abb1917774499c56f3c233aa19abe22f053fef3. No further alterations to the structure or content of the file are noted beyond these updates.

Possibly related PRs

• Update qtlseq to 2.2.5 #51172: Updates the version and SHA256 checksum in the meta.yaml file for the qtlseq package.
• Update qtlseq to 2.2.6 #51191: Similar to Update qtlseq to 2.2.5 #51172, this PR also updates the version and SHA256 checksum in the meta.yaml file for the qtlseq package.
• Update seqfu to 1.22.3 #51410: Updates the version and SHA256 checksum in the meta.yaml file for the seqfu package.
• Update qtlseq to 2.2.8 #51471: Involves updating the version and SHA256 checksum in the meta.yaml file for the qtlseq package, similar to changes made in the main PR.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 4c4e63a and 4ba2a2c.

📒 Files selected for processing (1)

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

🧰 Additional context used

🔇 Additional comments (3)

recipes/iseq/meta.yaml (3)

10-10: SHA256 checksum format is valid.

The new checksum follows the correct format (64 characters, hexadecimal).

Let's verify the checksum matches the release tarball:

#!/bin/bash
# Download the release tarball and verify its checksum
EXPECTED="9ddac60c63f774aac274de5a2abb1917774499c56f3c233aa19abe22f053fef3"
URL="https://github.com/BioOmics/iSeq/releases/download/v1.2.0/iSeq-v1.2.0.tar.gz"
ACTUAL=$(curl -sL "$URL" | sha256sum | cut -d' ' -f1)
echo "Expected: $EXPECTED"
echo "Actual  : $ACTUAL"
[ "$EXPECTED" = "$ACTUAL" ] && echo "Checksum verified ✓" || echo "Checksum mismatch ✗"

---

Line range hint 12-27: Verify dependency compatibility with new version.

The build configuration and dependencies look appropriate for a bash script. However, it's worth verifying if the pinned sra-tools version (2.11.0) is still compatible with the new release.

Let's check the changelog or release notes for any dependency changes:

#!/bin/bash
# Check release notes for dependency changes
gh release view --repo BioOmics/iSeq v1.2.0 | grep -i "dependency\|sra-tools" || echo "No dependency changes mentioned"

# Look for sra-tools version references in the script
curl -sL "https://github.com/BioOmics/iSeq/releases/download/v1.2.0/iSeq-v1.2.0.tar.gz" | tar xz -O 2>/dev/null | grep -i "sra-tools" || echo "No sra-tools version references found"

🧰 Tools

🪛 yamllint

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

(syntax)

---

2-2: Version update looks correct.

The version bump to 1.2.0 follows semantic versioning and matches the PR objectives.

Let's verify the release exists:

✅ Verification successful

Let me generate new shell scripts to verify the release existence using a different approach.

This will help us:

1. Verify if the release tarball exists and is accessible
2. Check if the release page exists
3. Cross-reference the package metadata to ensure consistency

---

Version 1.2.0 release exists and is accessible

The verification results show that:

1. The GitHub release page for v1.2.0 exists (HTTP 200 response)
2. The source tarball URL is valid (HTTP 302 redirect, which is normal for GitHub releases)
3. The version in meta.yaml (1.2.0) is consistent with the package metadata and source URL template

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify that the GitHub release exists and is accessible
gh release view --repo BioOmics/iSeq v1.2.0 2>/dev/null || echo "Release not found"

Length of output: 1817

---

Script:

#!/bin/bash
# Check if the tarball URL is accessible
curl -sI "https://github.com/BioOmics/iSeq/releases/download/v1.2.0/iSeq-v1.2.0.tar.gz" | head -n 1

# Also check the release page directly
curl -sI "https://github.com/BioOmics/iSeq/releases/tag/v1.2.0" | head -n 1

# Verify the package name and version in meta.yaml
cat recipes/iseq/meta.yaml

Length of output: 1061

---

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.

[BioOmics]

There are some other changes in meta.yml besides the version bump, see #51584 instead and ignore this one.