Update pbsv to 2.10.0

[BiocondaBot]

Update pbsv: 2.9.0 → 2.10.0

Info	Link or Description
Recipe	recipes/pbsv (click to view/edit other files)
Summary	pbsv - PacBio structural variant (SV) calling and analysis tools
Home	https://github.com/PacificBiosciences/pbbioconda
Releases
Recipe Maintainer(s)	@armintoepfer, @pb-dseifert
Author	@PacificBiosciences

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request involves updates to the meta.yaml file for the pbsv package. The version number has been incremented from "2.9.0" to "2.10.0", and the SHA256 checksum has been changed from "3daf41d28f5d0063f68c49ce790ab17b648f1d2459122f5c13704598342db97c" to "5b640017716efb2d30a75f5af5fd566eae8ee4d6b9517c0a903296b7d298121c". A new section has been added under build, which specifies run_exports with a pin for the pbsv subpackage, enhancing dependency management. Additionally, the about section has been updated to include a new dev_url field that points to the development repository. There are no other structural changes to the file, and the overall format remains consistent with the previous version.

Possibly related PRs

• Update pbskera to 1.3.0 #51734: This PR updates the pbskera package, which is related to the pbsv package, both developed by Pacific Biosciences, and involves changes to the version and SHA256 checksum in the meta.yaml file.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 98e6ec8 and 48c1f3d.

📒 Files selected for processing (1)

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

🔇 Additional comments (3)

recipes/pbsv/meta.yaml (3)

16-17: LGTM! Good addition of run_exports.

The addition of run_exports with max_pin="x" is a good practice. This ensures that dependent packages will maintain ABI compatibility by only allowing updates within the same major version.

---

27-27: LGTM! Good addition of development URL.

The addition of dev_url improves package metadata by providing users with a direct link to the development repository.

---

2-3: Verify checksum against official release.

The version bump and checksum update appear correct, but let's verify the checksum matches the official release.

---

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.

[jmattick]

Please see this PR: #51738