Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update agfusion to 1.4.3 #51041

Merged
merged 1 commit into from
Sep 30, 2024
Merged

Update agfusion to 1.4.3 #51041

merged 1 commit into from
Sep 30, 2024

Conversation

BiocondaBot
Copy link
Collaborator

@BiocondaBot BiocondaBot commented Sep 30, 2024

Update agfusion: 1.4.11.4.3

install with bioconda Conda

Info Link or Description
Recipe recipes/agfusion (click to view/edit other files)
Summary Python package to annotate and visualize gene fusions.
Home https://github.com/murphycj/AGFusion
Releases https://pypi.org/pypi/agfusion/json

This pull request was automatically generated (see docs).

Summary by CodeRabbit

  • New Features
    • Updated the agfusion package to version 1.4.3, which may include bug fixes and enhancements.
  • Chores
    • Updated the package source URL to reflect the new version.

@BiocondaBot BiocondaBot added autobump Automatic Version Update new version labels Sep 30, 2024
Copy link

coderabbitai bot commented Sep 30, 2024

📝 Walkthrough

Walkthrough

The pull request updates the meta.yaml file for the agfusion package. The version number is increased from "1.4.1" to "1.4.3", and the SHA256 checksum is modified to match the new version. Additionally, the source URL for the package has been updated accordingly. No other changes to the package structure, requirements, or metadata are included.

Changes

File Change Summary
recipes/agfusion/meta.yaml - Version updated from "1.4.1" to "1.4.3"
- SHA256 updated from "fd04591d764deeff69978f9d495c3baf854ccfba27366aa0ae4859ad85ca2c60" to "0fdace7fad64713173cac049af3783bdb3db406d5a6dafd4cc0c1948d0724c8f"
- Source URL updated for the new version

Possibly related PRs


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
🪧 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
recipes/agfusion/meta.yaml (1)

Dependencies Version Mismatch Detected

There are discrepancies between the setup.py and meta.yaml regarding the versions of matplotlib and pandas:

  • matplotlib:

    • setup.py requires >=1.5.0
    • meta.yaml requires >=3.6.1
  • pandas:

    • setup.py requires >=0.18.1
    • meta.yaml requires >=1.5.1

Please update the setup.py to match the meta.yaml requirements to ensure compatibility.

🔗 Analysis chain

Line range hint 4-50: Verify dependencies and metadata for the new version.

While the version update looks good, it's important to ensure that all dependencies and metadata are still accurate for version 1.4.3. Please verify:

  1. That all dependencies in the requirements section are still compatible with the new version.
  2. That the metadata in the about section (especially the summary and license) is still accurate.
  3. That the run_exports directive in the build section is still appropriate for this version.

To help with this verification, you can run the following script to check for any changes in the package's setup.py or README:

Review the output to ensure that no significant changes require updates to the recipe.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for changes in setup.py and README

# Test: Download the new version and check for changes in setup.py and README
curl -sL https://pypi.io/packages/source/a/agfusion/agfusion-1.4.3.tar.gz | tar -xz -O --wildcards '*/setup.py' '*/README*'

Length of output: 10357

🧰 Tools
🪛 yamllint

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

(syntax)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between c69d1bb and 3e38ae2.

📒 Files selected for processing (1)
  • recipes/agfusion/meta.yaml (1 hunks)
🧰 Additional context used
🪛 yamllint
recipes/agfusion/meta.yaml

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

(syntax)

🔇 Additional comments (2)
recipes/agfusion/meta.yaml (2)

Line range hint 1-50: Summary of changes and next steps

The changes in this PR are minimal and focused on updating the version from 1.4.1 to 1.4.3 and updating the corresponding SHA256 hash. These changes align with the PR objectives for a version bump.

Next steps:

  1. Verify the SHA256 hash using the provided script.
  2. Check the dependencies and metadata using the second script to ensure they're still accurate for version 1.4.3.
  3. If all verifications pass, this PR is ready to be merged.
🧰 Tools
🪛 yamllint

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

(syntax)


1-2: LGTM! Version and SHA256 hash updated correctly.

The version has been updated to 1.4.3 as per the PR objective, and the SHA256 hash has been updated accordingly. These changes are consistent with a standard version bump for the package.

Let's verify the SHA256 hash for the new version:

#!/bin/bash
# Description: Verify the SHA256 hash for agfusion-1.4.3.tar.gz

# Test: Download the package and compute its SHA256 hash
curl -sL https://pypi.io/packages/source/a/agfusion/agfusion-1.4.3.tar.gz | sha256sum

Please compare the output of this script with the SHA256 hash in the recipe to ensure they match.

🧰 Tools
🪛 yamllint

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

(syntax)

@apeltzer apeltzer enabled auto-merge (squash) September 30, 2024 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autobump Automatic Version Update new version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants