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 gget to 0.29.0 #50960

Merged
merged 2 commits into from
Sep 26, 2024
Merged

Update gget to 0.29.0 #50960

merged 2 commits into from
Sep 26, 2024

Conversation

BiocondaBot
Copy link
Collaborator

@BiocondaBot BiocondaBot commented Sep 26, 2024

Update gget: 0.28.60.29.0

install with bioconda Conda

Info Link or Description
Recipe recipes/gget (click to view/edit other files)
Summary gget enables efficient querying of genomic databases.
Home https://github.com/pachterlab/gget
Releases https://github.com/pachterlab/gget/tags
Recipe Maintainer(s) @nh13, @lauraluebbert
Author @pachterlab

This pull request was automatically generated (see docs).

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

coderabbitai bot commented Sep 26, 2024

📝 Walkthrough

Walkthrough

The meta.yaml file for the gget package has been updated to version 0.29.0 from 0.28.6, with changes including an updated SHA256 checksum, an increase in the Python version requirement from >=3.6 to >=3.7, and an update to the version constraint for mysql-connector-python from >=8.0.5,<=8.0.29 to >=8.0.32. Additionally, the summary description now includes a period at the end, and a new DOI identifier has been added.

Changes

File Change Summary
recipes/gget/meta.yaml - Version updated from 0.28.6 to 0.29.0
- SHA256 updated from 4cbc60e967... to 5af54af941...
- Python version requirement updated from >=3.6 to >=3.7
- MySQL connector version updated from >=8.0.5,<=8.0.29 to >=8.0.32
- Summary updated to include a period at the end
- DOI identifier added with value 10.1093/bioinformatics/btac836

Possibly related PRs

  • Update architeuthis to 0.3.1 #50970: The changes in the meta.yaml file for the architeuthis package involve updating the version and SHA256 checksum, similar to the updates made in the gget package's meta.yaml file.
  • Update stranger to 0.9.2 #50971: The stranger package's meta.yaml file also underwent a version and SHA256 checksum update, paralleling the changes in the gget package.
  • Update gbintk to 1.0.0 #50974: The gbintk package's meta.yaml file was updated with a new version and SHA256 checksum, reflecting a similar pattern to the updates in the gget package.
  • Update vsearch to 2.29.0 #50975: The vsearch package's meta.yaml file includes updates to the version and SHA256 checksum, akin to the modifications made in the gget package.
  • Update peaks2utr to 1.3.2 #50979: The peaks2utr package's meta.yaml file was updated with a new version and SHA256 checksum, mirroring the changes in the gget package.

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
Contributor

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

78-79: DOI identifier addition approved with a suggestion.

The addition of the DOI identifier is excellent as it enhances the metadata and improves the discoverability and citability of the package.

Consider adding a comment above the DOI to indicate what it refers to, for example:

  identifiers:
    # DOI for the gget publication
    - doi:10.1093/bioinformatics/btac836

This will provide more context for future maintainers and users of the recipe.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 600e0f6 and e8758e9.

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

2-3: Version and checksum update looks good.

The package version has been correctly updated to 0.29.0, and the SHA256 checksum has been updated accordingly. These changes are consistent with the PR objectives.


66-66: Summary formatting improvement approved.

The addition of a period at the end of the summary improves its formatting and consistency.


30-30: Verify mysql-connector-python version requirement change.

The mysql-connector-python version requirement has been updated from >=8.0.5,<=8.0.29 to >=8.0.32. This change significantly increases the minimum version and removes the upper bound constraint.

Please confirm if this change is intentional and required. Consider the following:

  1. Are there specific features or bug fixes in mysql-connector-python 8.0.32 that are necessary for gget 0.29.0?
  2. Is it safe to remove the upper bound constraint? This might lead to compatibility issues with future versions of mysql-connector-python.

You can run the following script to check if the change is mentioned in the release notes:

Also applies to: 43-43


24-24: Verify Python version requirement change.

The minimum Python version requirement has been increased from 3.6 to 3.7. While this change might be necessary for new features or dependencies in gget 0.29.0, it could potentially break compatibility for users still using Python 3.6.

Please confirm if this change is intentional and required. You can run the following script to check if the change is mentioned in the release notes:

Also applies to: 37-37

@BiocondaBot
Copy link
Collaborator Author

No artifacts found on the most recent builds. Either the builds failed, the artifacts have been removed due to age, or the recipe was blacklisted/skipped.

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