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 mycotools to 0.32.3 #51116

Merged
merged 1 commit into from
Oct 2, 2024
Merged

Update mycotools to 0.32.3 #51116

merged 1 commit into from
Oct 2, 2024

Conversation

BiocondaBot
Copy link
Collaborator

@BiocondaBot BiocondaBot commented Oct 2, 2024

Update mycotools: 0.32.20.32.3

install with bioconda Conda

Info Link or Description
Recipe recipes/mycotools (click to view/edit other files)
Summary Comparative genomics automation and standardization software.
Home https://github.com/xonq/mycotools
Releases https://pypi.org/pypi/mycotools/json
Recipe Maintainer(s) @xonq

This pull request was automatically generated (see docs).

Summary by CodeRabbit

  • New Features
    • Updated the mycotools package to version 0.32.3, ensuring users benefit from the latest improvements and features.
  • Bug Fixes
    • Enhanced integrity verification with an updated SHA256 checksum for the source tarball, ensuring a more secure installation.

@BiocondaBot BiocondaBot added autobump Automatic Version Update new version labels Oct 2, 2024
Copy link

coderabbitai bot commented Oct 2, 2024

📝 Walkthrough

Walkthrough

The pull request introduces an update to the meta.yaml file for the mycotools package. The version number is incremented from 0.32.2 to 0.32.3, and the SHA256 checksum for the source tarball is updated to a new value, replacing the previous checksum. No additional changes to the structure or content of the meta.yaml file are made.

Changes

File Change Summary
recipes/mycotools/meta.yaml Updated version from 0.32.2 to 0.32.3 and SHA256 checksum from 222111f17551... to 598caafca226...

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/mycotools/meta.yaml (1)

Line range hint 1-95: Overall changes look good, with a minor suggestion.

The version and SHA256 checksum updates are the only changes needed for this minor version update. All other sections of the recipe remain appropriately unchanged.

As a minor improvement, consider adding a build section to pin the Python version more precisely:

build:
  noarch: python
  number: 0
  script: {{ PYTHON }} -m pip install . -vv
  skip: True  # [py<36]

This ensures the package is built only for Python 3.6 and above, which is consistent with the python >=3 requirement in the run section.

🧰 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 38857c4 and f733f3f.

📒 Files selected for processing (1)
  • recipes/mycotools/meta.yaml (1 hunks)
🔇 Additional comments (2)
recipes/mycotools/meta.yaml (2)

2-2: Version update looks good.

The version has been correctly updated from 0.32.2 to 0.32.3, which is consistent with the PR objectives.


10-10: Verify the SHA256 checksum.

The SHA256 checksum has been updated, which is necessary for the new version. However, we should verify that this checksum is correct for the new source package.

To verify the SHA256 checksum, run the following script:

@mencian mencian merged commit 8b31e67 into master Oct 2, 2024
7 checks passed
@mencian mencian deleted the bump/mycotools branch October 2, 2024 21:08
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