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 core-snp-filter to 0.2.0 #52219

Merged
merged 3 commits into from
Nov 20, 2024
Merged

Update core-snp-filter to 0.2.0 #52219

merged 3 commits into from
Nov 20, 2024

Conversation

BiocondaBot
Copy link
Collaborator

Update core-snp-filter: 0.1.10.2.0

install with bioconda Conda

Info Link or Description
Recipe recipes/core-snp-filter (click to view/edit other files)
Summary Filtering sites (i.e. columns) in a FASTA-format whole-genome pseudo-alignment.
Home https://github.com/rrwick/Core-SNP-filter
Releases https://github.com/rrwick/Core-SNP-filter/tags
Author @rrwick

This pull request was automatically generated (see docs).

@BiocondaBot BiocondaBot added autobump Automatic Version Update new version labels Nov 20, 2024
Copy link
Contributor

coderabbitai bot commented Nov 20, 2024

📝 Walkthrough

Walkthrough

The pull request introduces modifications to the meta.yaml file of the core-snp-filter package. The version number has been incremented from "0.1.1" to "0.2.0", indicating a new release of the package. Correspondingly, the source URL has been updated to reflect this new version, changing from the previous tarball URL for version "0.1.1" to the new URL for version "0.2.0". Additionally, the SHA256 checksum has been revised to a new value, which is necessary due to the changes in the source package. The build number has been reset from 1 to 0, suggesting a fresh build process for the updated package version. A new section for run_exports has been added, including a pinning directive for the core-snp-filter subpackage. The requirements section now references the Rust compiler using a compiler function instead of a version constraint. No changes have been made to the test commands or the overall metadata associated with the package.

Possibly related PRs

  • Update kmer-db #49740: The changes in the meta.yaml file for kmer-db include updates to the version, build number, and the addition of a run_exports section, which is similar to the updates made in the meta.yaml file for core-snp-filter.
  • Update meta.yaml for spec2vec #49857: The meta.yaml file for spec2vec also includes a version update and the addition of a run_exports section, paralleling the changes made in the core-snp-filter meta.yaml.
  • tidk v0.2.62 #50836: The meta.yaml file for tidk features a version update and the addition of the Rust compiler in the build requirements, which aligns with the changes made in the core-snp-filter meta.yaml.
  • Add dbghaplo #51035: The meta.yaml for dbghaplo includes updates to the version and build requirements, similar to the changes in the core-snp-filter meta.yaml.
  • Rebuild breseq #51221: The meta.yaml for breseq has a build number increment and updates to the requirements, which is consistent with the changes in the core-snp-filter meta.yaml.
  • Update vclean to 0.2.1 #51223: The meta.yaml for vclean reflects a version update, akin to the version change in the core-snp-filter meta.yaml.
  • Add snipe #51513: The meta.yaml for snipe includes a version update and a run_exports section, similar to the changes in the core-snp-filter meta.yaml.
  • Update diamond recipe #51515: The meta.yaml for diamond has a build number increment and updates to the requirements, paralleling the changes in the core-snp-filter meta.yaml.
  • version update #51524: The meta.yaml for strainy features a version update and a change in the build number, consistent with the updates in the core-snp-filter meta.yaml.
  • Update sainsc to 0.2.1 #51717: The meta.yaml for sainsc includes a version update, similar to the version change in the core-snp-filter meta.yaml.
  • Add Instanovo #51796: The meta.yaml for instanovo features a version update and a run_exports section, akin to the changes in the core-snp-filter meta.yaml.
  • Update meta-neuro version 1.0.0 #51826: The meta.yaml for meta-neuro includes a version update and a run_exports section, similar to the changes in the core-snp-filter meta.yaml.
  • Update snipe to 0.1.6 #51945: The meta.yaml for snipe reflects a version update, consistent with the version change in the core-snp-filter meta.yaml.
  • Update reseek to 2.02 #52032: The meta.yaml for reseek features a version update, akin to the version change in the core-snp-filter meta.yaml.
  • Update sniffles to 2.5.2 #52049: The meta.yaml for sniffles includes a version update and changes to the requirements, similar to the updates in the core-snp-filter meta.yaml.
  • Edited the build.sh and mata.yaml files #52085: The meta.yaml for sfold features a build number increment and a new runtime requirement, consistent with the changes in the core-snp-filter meta.yaml.
  • Update pacu_snp to 0.0.6 #52094: The meta.yaml for pacu_snp includes a version update, similar to the version change in the core-snp-filter meta.yaml.
  • Update snipit to 1.6 #52098: The meta.yaml for snipit features a version update, consistent with the version change in the core-snp-filter meta.yaml.
  • Update svtopovz to 0.2.1 #52147: The meta.yaml for svtopovz includes a version update, akin to the version change in the core-snp-filter meta.yaml.
  • Update unikseq to 2.0.0 #52169: The meta.yaml for unikseq features a version update, similar to the version change in the core-snp-filter meta.yaml.
  • Update oakvar to 2.12.4 #52218: The meta.yaml for oakvar includes a version update, consistent with the version change in the core-snp-filter meta.yaml.

Warning

Rate limit exceeded

@mencian has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 25 minutes and 10 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 89e3395 and 3a7087d.


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/core-snp-filter/meta.yaml (1)

Line range hint 1-40: Overall package update looks good

The update to core-snp-filter 0.2.0 includes several improvements:

  1. Proper version bump with reset build number
  2. Better compiler specification
  3. Added run_exports for improved ABI compatibility

The changes follow bioconda best practices and include appropriate updates to all required fields.

Consider adding a test.requires section if there are any runtime dependencies needed specifically for testing.

🧰 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

Reviewing files that changed from the base of the PR and between 89e3395 and 3a7087d.

📒 Files selected for processing (2)
  • recipes/core-snp-filter/build.sh (0 hunks)
  • recipes/core-snp-filter/meta.yaml (1 hunks)
💤 Files with no reviewable changes (1)
  • recipes/core-snp-filter/build.sh
🧰 Additional context used
🪛 yamllint
recipes/core-snp-filter/meta.yaml

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

(syntax)

🔇 Additional comments (4)
recipes/core-snp-filter/meta.yaml (4)

12-14: LGTM! Good improvements to package compatibility

The changes look good:

  • Build number correctly reset to 0 for the new version
  • Addition of run_exports with appropriate pinning will help maintain ABI compatibility

20-20: LGTM! Better compiler specification

The change from rust >=1.39 to {{ compiler('rust') }} is an improvement as it:

  • Follows conda-forge/bioconda best practices
  • Provides better build-time compiler handling

1-1: Verify upstream version tag existence

The version bump from 0.1.1 to 0.2.0 indicates new features. Let's verify the tag exists in the upstream repository.

✅ Verification successful

Version 0.2.0 is correctly tagged in upstream repository

The version bump from 0.1.1 to 0.2.0 is valid. The tag v0.2.0 exists in the upstream repository (rrwick/Core-SNP-filter) and is the latest release tag, following the previous versions v0.1.1 and v0.1.0.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that v0.2.0 tag exists in the upstream repository
gh api repos/rrwick/Core-SNP-filter/git/refs/tags/v0.2.0 --silent || echo "Tag v0.2.0 not found"

Length of output: 67


Script:

#!/bin/bash
# Let's try a different approach to verify the version
# 1. Check if the repository exists and get basic info
gh api repos/rrwick/Core-SNP-filter

# 2. List all tags to see available versions
gh api repos/rrwick/Core-SNP-filter/tags

Length of output: 6758

🧰 Tools
🪛 yamllint

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

(syntax)


8-9: Verify source tarball checksum

Let's verify the SHA256 checksum matches the source tarball.

@mencian mencian merged commit 4c6e870 into master Nov 20, 2024
6 checks passed
@mencian mencian deleted the bump/core_snp_filter branch November 20, 2024 07:51
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