Update snk-cli to 0.5.5

[BiocondaBot]

Update snk-cli: 0.5.4 → 0.5.5

Info	Link or Description
Recipe	recipes/snk-cli (click to view/edit other files)
Summary	Dynamically generate CLIs from Snakemake configuration files
Home	https://github.com/wytamma/snk-cli
Releases	https://pypi.org/pypi/snk_cli/json
Recipe Maintainer(s)	@Wytamma

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces an update to the meta.yaml file for the snk-cli package. The primary changes include an increment in the version number from 0.5.4 to 0.5.5, reflecting a new release of the package. Additionally, the SHA256 checksum for the source tarball has been updated to a new value, 5ba6a88aca3473751152cdcd22b0cdc31b0f4034d9eabf859a3dfc6dcc4a487f, replacing the previous checksum 570b8dd7427a11486d90e14c4fb8231169af44b8e36c36c6b6aa5b9b00710c66. No other modifications to the structure or content of the meta.yaml file have been made.

Possibly related PRs

• Add Snk-CLI #51153: This PR updates the meta.yaml file for the snk-cli package, which is directly related to the main PR that also modifies the meta.yaml for snk-cli, specifically updating the version and SHA256 checksum.
• Update snk-cli to 0.5.4 #51233: This PR updates the meta.yaml file for the snk-cli package from version 0.5.2 to 0.5.4, which is relevant as the main PR updates the version from 0.5.4 to 0.5.5, indicating a close relationship in versioning changes.

Suggested reviewers

• martin-g: Suggested reviewer for this PR.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 99770b7 and 88c8b55.

📒 Files selected for processing (1)

• recipes/snk-cli/meta.yaml (1 hunks)

🧰 Additional context used

🔇 Additional comments (3)

recipes/snk-cli/meta.yaml (3)

2-2: Version update looks correct.

The version has been updated from 0.5.4 to 0.5.5, which aligns with the PR objectives.

---

Line range hint 1-55: Overall recipe structure looks good.

The recipe structure is appropriate for a Python package:

• It correctly specifies noarch: python.
• Dependencies are well-defined in both host and run sections.
• Test section includes import tests and a pip check.
• Metadata is properly provided in the about section.
• The recipe maintainer is listed in the extra section.

No additional changes seem necessary as a result of this version bump.

🧰 Tools

🪛 yamllint

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

(syntax)

---

10-10: Verify SHA256 checksum.

The SHA256 checksum has been updated. Let's verify its correctness.

---

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.