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 vsearch to 2.29.0 #50975

Merged
merged 1 commit into from
Sep 26, 2024
Merged

Update vsearch to 2.29.0 #50975

merged 1 commit into from
Sep 26, 2024

Conversation

BiocondaBot
Copy link
Collaborator

@BiocondaBot BiocondaBot commented Sep 26, 2024

Update vsearch: 2.28.12.29.0

install with bioconda Conda

Info Link or Description
Recipe recipes/vsearch (click to view/edit other files)
Summary A versatile open source tool for metagenomics (USEARCH alternative)
Home https://github.com/torognes/vsearch
Releases https://github.com/torognes/vsearch/tags
Author @torognes

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

The pull request includes updates to the meta.yaml file for the vsearch package. The version number has been increased from "2.28.1" to "2.29.0". The SHA256 checksum has been modified to reflect this new version, and the build number has been reset from 1 to 0. These changes indicate a new release of the package.

Changes

File Change Summary
recipes/vsearch/meta.yaml Version updated from "2.28.1" to "2.29.0"; SHA256 updated from "4f8bf0ad..." to "2c5bd0d9..."; Build number changed from 1 to 0.

Poem

In the garden of code, a new version blooms,
With a SHA256 dance, it brightens the rooms.
From "2.28" to "2.29" it leaps,
A reset of builds, as the rabbit softly peeps.
Hopping along, we celebrate with cheer,
For vsearch is fresh, and the future is clear! 🐇✨


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

Line range hint 35-37: Consider enhancing the test section.

While the current test section is functional, it might be beneficial to include more visible tests directly in the meta.yaml file. This could provide better transparency and easier maintenance of the package.

Consider adding a few key test commands directly in the meta.yaml file, such as:

test:
  commands:
    - vsearch --version
    - vsearch --help
    - vsearch --allpairs_global small.fna.gz --blast6out - | grep -q "^[0-9]"

This would provide a quick sanity check of basic functionality without relying entirely on the external run_tests.sh file.

🧰 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 d6403ea and 2cc55a5.

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

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

(syntax)

🔇 Additional comments (3)
recipes/vsearch/meta.yaml (3)

1-1: Version update looks good.

The version has been correctly updated to 2.29.0, which aligns with the PR objectives.

🧰 Tools
🪛 yamllint

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

(syntax)


13-13: Build number reset is correct.

The build number has been appropriately reset to 0 for the new version. This aligns with Conda packaging best practices.


2-2: Verify the SHA256 checksum.

The SHA256 checksum has been updated for the new version. It's crucial to ensure this checksum is correct for vsearch 2.29.0.

Run the following script to verify the SHA256 checksum:

If the script output shows "OK", the checksum is correct.

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

@BiocondaBot
Copy link
Collaborator Author

Package(s) built are ready for inspection:

Arch Package Zip File / Repodata CI Instructions
osx-arm64 vsearch-2.29.0-he5cb1a1_0.tar.bz2 repodata.json CircleCI
showYou may also use conda to install:conda install -c https://output.circle-artifacts.com/output/job/204b3617-ff04-480d-b487-aae6120f1da3/artifacts/0/tmp/artifacts/packages <package name>

1 similar comment
@BiocondaBot
Copy link
Collaborator Author

Package(s) built are ready for inspection:

Arch Package Zip File / Repodata CI Instructions
osx-arm64 vsearch-2.29.0-he5cb1a1_0.tar.bz2 repodata.json CircleCI
showYou may also use conda to install:conda install -c https://output.circle-artifacts.com/output/job/204b3617-ff04-480d-b487-aae6120f1da3/artifacts/0/tmp/artifacts/packages <package name>

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