Update dnaio to 1.2.3

[BiocondaBot]

Update dnaio: 1.2.2 → 1.2.3

Info	Link or Description
Recipe	recipes/dnaio (click to view/edit other files)
Summary	Read and write FASTA and FASTQ files efficiently
Home	https://github.com/marcelm/dnaio/
Releases	https://pypi.org/pypi/dnaio/json
Recipe Maintainer(s)	@marcelm

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

📝 Walkthrough

Walkthrough

The pull request updates the meta.yaml file for the dnaio package, changing the version from "1.2.2" to "1.2.3". The source URL has been modified to point to the new version's tarball at dnaio-1.2.3.tar.gz, and the SHA256 checksum has been updated to aad456d9f6272339958b2c5af32fd64d77a50aca12e394e7a143b4129d49b0b9. Additionally, the Python version requirement has been changed from python to python >=3.9 in both the host and run sections of the requirements. All other sections of the meta.yaml file, including build, test, about, and extra, remain unchanged.

Possibly related PRs

• Update dnaio to 1.2.2 #51157: This PR updates the dnaio package from version 1.2.1 to 1.2.2, which is directly related to the main PR that updates dnaio from 1.2.2 to 1.2.3.
• Update dnaio dependency for cutadapt #51188: This PR updates the cutadapt package to depend on dnaio >=1.2.2, which is relevant as the main PR updates dnaio to a newer version.
• [biobb_dna] update 5.0.0 #51601: This PR updates the biobb_dna package to require python >=3.9, which aligns with the main PR's change to the Python version requirement in dnaio.

Suggested reviewers

• rhpvorderman

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between cde141e and 5528e3e.

📒 Files selected for processing (1)

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

🧰 Additional context used

🪛 yamllint

recipes/dnaio/meta.yaml

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

(syntax)

🔇 Additional comments (3)

recipes/dnaio/meta.yaml (3)

1-1: LGTM: Version update is consistent

The version bump to 1.2.3 matches the PR objectives and is correctly referenced in the package metadata.

🧰 Tools

🪛 yamllint

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

(syntax)

---

8-9: Verify source integrity

The source URL and checksum have been updated for version 1.2.3.

---

23-23: Verify Python version constraint change

The addition of python >=3.9 constraint is a breaking change that could affect compatibility with dependent packages.

Consider documenting this breaking change in the package release notes and ensuring all dependent packages in the bioconda ecosystem are compatible with Python >=3.9.

Also applies to: 27-27

---

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.