Update nanovar to 1.8.0

[BiocondaBot]

Update nanovar: 1.5.1 → 1.8.0

Info	Link or Description
Recipe	recipes/nanovar (click to view/edit other files)
Summary	Structural variant caller using low-depth long reads
Home	https://github.com/cytham/nanovar
Releases	https://pypi.org/pypi/nanovar/json
Recipe Maintainer(s)	@cytham

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

📝 Walkthrough

Walkthrough

The pull request updates the meta.yaml file for the nanovar package. It increments the package version from "1.5.1" to "1.8.0", modifies the source URL to reflect the new version, and updates the SHA256 checksum accordingly. Additionally, the build number is changed from 1 to 0, while the build script remains unchanged. The requirements section has been updated, including an increase in the minimum version for biopython and the addition of tensorflow-cpu.

Changes

File	Change Summary
recipes/nanovar/meta.yaml	- Version updated from "1.5.1" to "1.8.0" - Source URL updated to new version's tarball - SHA256 checksum updated - Build number changed from 1 to 0 - Minimum version for biopython increased from 1.78 to 1.82 - Added tensorflow-cpu dependency with version range - Dependencies reordered without changing minimum versions

Possibly related PRs

• Update architeuthis to 0.3.1 #50970: Updates the version, SHA256 checksum, and build number in the meta.yaml file, similar to the main PR for the nanovar package.
• Update stranger to 0.9.2 #50971: Similar updates to the version and SHA256 checksum in the meta.yaml file.
• Update gbintk to 1.0.0 #50974: Aligns with the changes made in the main PR by updating the version and SHA256 checksum in the meta.yaml file for the gbintk package.
• Update peaks2utr to 1.3.2 #50979: Updates the version, SHA256 checksum, and source URL in the meta.yaml file, paralleling 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 6fde72f and 8e5697b.

📒 Files selected for processing (1)

• recipes/nanovar/meta.yaml (2 hunks)

🧰 Additional context used

🪛 yamllint

recipes/nanovar/meta.yaml

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

(syntax)

🔇 Additional comments (6)

recipes/nanovar/meta.yaml (6)

1-1: LGTM: Version update is correct.

The package version has been correctly updated to 1.8.0, which aligns with the PR objectives.

🧰 Tools

🪛 yamllint

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

(syntax)

---

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

The build number has been correctly reset to 0 for the new version, which is the standard practice when updating to a new package version.

---

28-28: Verify compatibility with updated biopython version.

The minimum required version of biopython has been increased from 1.78 to 1.82. Please ensure that this change is necessary for nanovar 1.8.0 and doesn't introduce any compatibility issues.

---

31-31: New dependency: tensorflow-cpu

A new dependency on tensorflow-cpu has been added with a specific version range. This is a significant change that might indicate new features or requirements in nanovar 1.8.0.

Please confirm:

1. Is this dependency necessary for the new version of nanovar?
2. Are there any implications for users upgrading from the previous version?
3. Does this change require updates to the package documentation or usage instructions?

---

30-34: Dependency changes and reordering

The dependencies have been reordered, and the 'progress' dependency seems to have been removed. While reordering doesn't affect functionality, please confirm:

1. Is the removal of the 'progress' dependency intentional?
2. If so, has this change been properly documented in the package's changelog or release notes?

---

9-9: Verify the SHA256 checksum.

The SHA256 checksum has been updated for the new version. Please ensure that this checksum is correct for the nanovar-1.8.0.tar.gz file.

Run the following script to verify the checksum:

---

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.

[BiocondaBot]

No artifacts found on the most recent builds. Either the builds failed, the artifacts have been removed due to age, or the recipe was blacklisted/skipped.

[BiocondaBot]

No artifacts found on the most recent builds. Either the builds failed, the artifacts have been removed due to age, or the recipe was blacklisted/skipped.

[BiocondaBot]

No artifacts found on the most recent builds. Either the builds failed, the artifacts have been removed due to age, or the recipe was blacklisted/skipped.

[BiocondaBot]

No artifacts found on the most recent builds. Either the builds failed, the artifacts have been removed due to age, or the recipe was blacklisted/skipped.