Update resistify to 0.4.0

[BiocondaBot]

Update resistify: 0.3.0 → 0.4.0

Info	Link or Description
Recipe	recipes/resistify (click to view/edit other files)
Summary	A resistance gene annotation tool
Home	https://github.com/swiftseal/resistify
Releases	https://pypi.org/pypi/resistify/json

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request involves an update to the meta.yaml file for the resistify package. The primary changes include incrementing the version number from 0.3.0 to 0.4.0 and updating the SHA256 checksum of the source package from 3a8f4ccedf38fb1a7cdb3522ad6497d054bd72164155bcdc03aa23133b030623 to ba06333873fcb1e07820cb0895755b42a615d289437749846e280bc87d6abf2c. These modifications are the only alterations made to the meta.yaml file, with no structural or content changes beyond the version and checksum updates.

Possibly related PRs

• Update versionix to 0.99.0 #51204: The version and sha256 in the meta.yaml file for the versionix package were updated from 0.3.0 to 0.99.0.
• Update ont-modkit to 0.4.1 #51025: The meta.yaml file for the ont-modkit package was updated with a version change from 0.4.0 to 0.4.1.
• Update pcaone to 0.4.6 #51130: The meta.yaml file for the pcaone package was updated, changing the version from 0.4.5 to 0.4.6.
• Update r-grain to 1.4.3 #51261: The r-grain package's meta.yaml file was updated with a version change from 1.4.2 to 1.4.3.
• Update r-grain to 1.4.4 #51313: The r-grain package's version was updated from 1.4.3 to 1.4.4.
• Update nanomotif to 0.4.14 #51275: The nanomotif package's meta.yaml file was updated from version 0.4.13 to 0.4.14.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 1c1935d and c8bed6a.

📒 Files selected for processing (1)

• recipes/resistify/meta.yaml (1 hunks)

🧰 Additional context used

🔇 Additional comments (3)

recipes/resistify/meta.yaml (3)

2-2: Version update looks good.

The version has been correctly updated from 0.3.0 to 0.4.0, which aligns with the PR objectives.

---

10-10: Verify the SHA256 checksum.

The SHA256 checksum has been updated. Please ensure that this new checksum corresponds to the correct source package for resistify version 0.4.0.

To verify the checksum, you can run the following script:

#!/bin/bash
# Description: Verify the SHA256 checksum of the resistify 0.4.0 package

# Download the package
curl -L -o resistify-0.4.0.tar.gz https://pypi.io/packages/source/r/resistify/resistify-0.4.0.tar.gz

# Calculate the SHA256 checksum
calculated_checksum=$(sha256sum resistify-0.4.0.tar.gz | awk '{print $1}')

# Compare with the checksum in the meta.yaml
expected_checksum="ba06333873fcb1e07820cb0895755b42a615d289437749846e280bc87d6abf2c"

if [ "$calculated_checksum" = "$expected_checksum" ]; then
    echo "Checksum verification passed."
else
    echo "Checksum verification failed."
    echo "Calculated: $calculated_checksum"
    echo "Expected:   $expected_checksum"
fi

# Clean up
rm resistify-0.4.0.tar.gz

---

Line range hint 1-47: Verify if any other changes are necessary for this version update.

The version and checksum have been updated, but no other changes have been made to the meta.yaml file. Please confirm that:

1. The new version (0.4.0) doesn't introduce any new dependencies.
2. The existing dependencies don't require version updates.
3. The Python version requirement (>=3.9) is still valid for the new version.

You can verify this by checking the package's release notes or requirements file for version 0.4.0.

To assist in this verification, you can run the following script to check for any changes in the package's setup file or requirements:

If this script shows any significant changes, please update the meta.yaml file accordingly.

✅ Verification successful

Verified that no additional changes are necessary for the version update.

• Only the version in pyproject.toml was updated.
• No new dependencies were introduced.
• Existing dependencies and Python version requirement remain unchanged.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for changes in setup.py or requirements.txt between versions

# Clone the repository
git clone https://github.com/swiftseal/resistify.git
cd resistify

# Check for changes in setup.py or requirements.txt between v0.3.0 and v0.4.0
git diff v0.3.0 v0.4.0 -- setup.py pyproject.toml requirements.txt

# Clean up
cd ..
rm -rf resistify

Length of output: 545

---

Script:

#!/bin/bash
# Description: List all git tags to verify if v0.3.0 and v0.4.0 exist

cd resistify || exit
git fetch --all --tags
git tag

Length of output: 110

---

Script:

#!/bin/bash
# Description: Remove existing resistify directory, clone the repository, and list all git tags

# Remove existing resistify directory if it exists
rm -rf resistify

# Clone the resistify repository
git clone https://github.com/swiftseal/resistify.git

# Navigate into the repository
cd resistify || exit

# Fetch all tags from the remote repository
git fetch --all --tags

# List all git tags to verify the presence of v0.3.0 and v0.4.0
git tag

Length of output: 248

---

Script:

#!/bin/bash
# Description: Compare setup.py, pyproject.toml, and requirements.txt between v0.3.0 and v0.4.0

# Navigate into the repository
cd resistify || exit

# Show differences between v0.3.0 and v0.4.0 for specified files
git diff v0.3.0 v0.4.0 -- setup.py pyproject.toml requirements.txt

Length of output: 382

🧰 Tools

🪛 yamllint

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

(syntax)

---

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.