Update snakemake-executor-plugin-kubernetes to 0.2.2

[BiocondaBot]

Update snakemake-executor-plugin-kubernetes: 0.2.1 → 0.2.2

Info	Link or Description
Recipe	recipes/snakemake-executor-plugin-kubernetes (click to view/edit other files)
Summary	A snakemake executor plugin for submission of jobs to Kubernetes
Home	https://github.com/snakemake/snakemake-executor-plugin-kubernetes
Releases	https://pypi.org/pypi/snakemake_executor_plugin_kubernetes/json
Recipe Maintainer(s)	@koesterlab

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces an update to the snakemake-executor-plugin-kubernetes package, specifically changing its version from 0.2.1 to 0.2.2. Along with this version change, the SHA256 checksum for the package source has been updated to ensure the integrity of the package. The previous checksum 476c423cb33b71bff2ed11d2ec0aace8bb76e1b9667b408880bcbe2c7fdbe6ef has been replaced with a new checksum 08f7ea92cc288f0830f7bfc38112c9e4a03d623d84f8f80b0105cc179458fc4c. These modifications are contained within the meta.yaml file located in the recipes/snakemake-executor-plugin-kubernetes directory. The changes are focused solely on versioning and checksum updates without any additional alterations to functionality or dependencies.

Possibly related PRs

• Update snakemake-interface-executor-plugins to 9.3.1 #51166: Update snakemake-interface-executor-plugins to 9.3.1 - This PR updates the version and SHA256 checksum in the meta.yaml file for a Snakemake executor plugin, similar to the version and checksum updates in the main PR for the snakemake-executor-plugin-kubernetes.
• Update snakemake-interface-executor-plugins to 9.3.2 #51180: Update snakemake-interface-executor-plugins to 9.3.2 - This PR also updates the version and SHA256 checksum in the meta.yaml file for the same Snakemake executor plugin, reflecting a similar type of change as in the main PR.
• Update snakemake to 8.20.6 #51219: Update snakemake to 8.20.6 - This PR updates the version and SHA256 checksum for the Snakemake package and modifies the dependency version for snakemake-interface-executor-plugins, indicating a related context to the main PR's focus on Snakemake plugins.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 83e229c and 2ae27f1.

📒 Files selected for processing (1)

• recipes/snakemake-executor-plugin-kubernetes/meta.yaml (2 hunks)

🧰 Additional context used

🔇 Additional comments (3)

recipes/snakemake-executor-plugin-kubernetes/meta.yaml (3)

11-11: SHA256 checksum updated. Verify its correctness.

The SHA256 checksum has been updated, which is necessary for the new version.

To ensure the integrity of the package, please verify that this checksum is correct for the new version. You can do this by running:

This script will download the package, calculate its checksum, and compare it with the one in the recipe.

---

2-2: Version update looks good. Remember to check requirements.

The version update from 0.2.1 to 0.2.2 is correct and aligns with the PR objectives.

As per the comment above this line, please ensure that the requirements have been checked and are up-to-date for this new version. You can verify this by running:

If there are any differences, please update the requirements section accordingly.

✅ Verification successful

Version update looks good. Dependencies remain unchanged.

The update from version 0.2.1 to 0.2.2 is correct and aligns with the PR objectives. No changes in dependencies were detected, so there’s no need for further checks on requirements.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if requirements have changed in the new version

# Fetch the requirements for both versions
curl -s https://raw.githubusercontent.com/snakemake/snakemake-executor-plugin-kubernetes/v0.2.1/pyproject.toml | grep -A 20 '\[tool\.poetry\.dependencies\]' > old_req.txt
curl -s https://raw.githubusercontent.com/snakemake/snakemake-executor-plugin-kubernetes/v0.2.2/pyproject.toml | grep -A 20 '\[tool\.poetry\.dependencies\]' > new_req.txt

# Compare the requirements
diff old_req.txt new_req.txt

# Clean up
rm old_req.txt new_req.txt

Length of output: 9582

---

Script:

#!/bin/bash
# Description: Fetch and compare dependencies between versions v0.2.1 and v0.2.2

# Fetch pyproject.toml for version v0.2.1
curl -s https://raw.githubusercontent.com/snakemake/snakemake-executor-plugin-kubernetes/v0.2.1/pyproject.toml -o v0.2.1_pyproject.toml
if [ $? -ne 0 ]; then
  echo "Failed to fetch pyproject.toml for v0.2.1"
  exit 1
fi

# Fetch pyproject.toml for version v0.2.2
curl -s https://raw.githubusercontent.com/snakemake/snakemake-executor-plugin-kubernetes/v0.2.2/pyproject.toml -o v0.2.2_pyproject.toml
if [ $? -ne 0 ]; then
  echo "Failed to fetch pyproject.toml for v0.2.2"
  exit 1
fi

# Extract dependencies using grep (assuming dependencies are listed under [tool.poetry.dependencies])
grep -A 100 '^\[tool\.poetry\.dependencies\]' v0.2.1_pyproject.toml | grep -v '^\[' > deps_v0.2.1.txt
grep -A 100 '^\[tool\.poetry\.dependencies\]' v0.2.2_pyproject.toml | grep -v '^\[' > deps_v0.2.2.txt

# Compare the dependencies
diff deps_v0.2.1.txt deps_v0.2.2.txt > deps_diff.txt

# Output the differences
if [ -s deps_diff.txt ]; then
  echo "Dependencies have changed between v0.2.1 and v0.2.2:"
  cat deps_diff.txt
else
  echo "No changes in dependencies between v0.2.1 and v0.2.2."
fi

# Clean up
rm v0.2.1_pyproject.toml v0.2.2_pyproject.toml deps_v0.2.1.txt deps_v0.2.2.txt deps_diff.txt

Length of output: 761

---

Line range hint 1-48: Consider checking the changelog for potential metadata updates.

The changes for this version bump are minimal and appropriate. However, it's always a good practice to review the changelog for the new version.

Please check if version 0.2.2 introduces any new features, bug fixes, or changes that might require updates to the package metadata or dependencies. You can do this by running:

This will help ensure that the package recipe accurately reflects any changes in the new version.

---

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.