Update sawfish to 0.12.6

[BiocondaBot]

Update sawfish: 0.12.5 → 0.12.6

Info	Link or Description
Recipe	recipes/sawfish (click to view/edit other files)
Summary	Structural variant discovery and genotyping from mapped PacBio HiFi data
Home	https://github.com/PacificBiosciences/sawfish
Releases
Recipe Maintainer(s)	@ctsa
Author	@PacificBiosciences

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates the meta.yaml file for the sawfish package. The version number has been incremented from 0.12.5 to 0.12.6. Along with the version change, the SHA256 checksum for the source tarball has been updated to reflect the new version, changing from fefbeb104a6784bbe7a1cb39470054cf25136ce75540547b63e4fb74fa614c7e to 15e9c190877bde4b01b3c72037459fa67d5183ad1172878ccd364807fcff51a8. Additionally, the source URL has been modified to point to the new version's download link, changing from https://github.com/PacificBiosciences/sawfish/releases/download/v0.12.5/sawfish-v0.12.5-x86_64-unknown-linux-gnu.tar.gz to https://github.com/PacificBiosciences/sawfish/releases/download/v0.12.6/sawfish-v0.12.6-x86_64-unknown-linux-gnu.tar.gz. No other modifications to the structure or content of the file are present.

Possibly related PRs

• MaxBin2 installation issue #51292: Update sawfish to 0.12.5
  • This PR updates the sawfish package's version and SHA256 checksum in the same meta.yaml file as the main PR, indicating a direct relationship in the versioning process.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 636aa38 and 9d1aab3.

📒 Files selected for processing (1)

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

🧰 Additional context used

🔇 Additional comments (4)

recipes/sawfish/meta.yaml (4)

2-2: Version update looks good.

The version has been correctly updated from 0.12.5 to 0.12.6, which aligns with the PR objectives.

---

Line range hint 1-35: Overall changes look good, and version pinning is correctly handled.

The necessary updates for version 0.12.6 have been made correctly. The run_exports section in the build field uses Jinja2 templating to automatically update the pinned version, so no manual changes were needed there.

🧰 Tools

🪛 yamllint

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

(syntax)

---

10-10: SHA256 checksum has been updated.

The SHA256 checksum has been changed to reflect the new version of the package.

Let's verify the correctness of the new SHA256 checksum:

---

9-9: Source URL update is correct.

The source URL has been properly updated to reflect the new version 0.12.6.

Let's verify the existence of the new release:

✅ Verification successful

Source URL verification passed.

The updated source URL is valid and the release is accessible.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the existence of the new release on GitHub

# Test: Check if the URL returns a 200 status code
curl -s -o /dev/null -w "%{http_code}" https://github.com/PacificBiosciences/sawfish/releases/download/v0.12.6/sawfish-v0.12.6-x86_64-unknown-linux-gnu.tar.gz

Length of output: 318

---

Script:

#!/bin/bash
# Description: Verify the existence of the new release on GitHub

# Test: Check if the URL returns a 200 status code
curl -s -o /dev/null -w "%{http_code}" https://github.com/PacificBiosciences/sawfish/releases/download/v0.12.6/sawfish-v0.12.6-x86_64-unknown-linux-gnu.tar.gz

Length of output: 164

---

Script:

#!/bin/bash
# Description: Verify the existence of the new release on GitHub by following redirects

# Test: Follow redirects and check the final HTTP status code
curl -s -o /dev/null -w "%{http_code}" -L https://github.com/PacificBiosciences/sawfish/releases/download/v0.12.6/sawfish-v0.12.6-x86_64-unknown-linux-gnu.tar.gz

Length of output: 167

---

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.