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 PhaBOX to 2.1.6 #52264

Merged
merged 2 commits into from
Nov 21, 2024
Merged

Update PhaBOX to 2.1.6 #52264

merged 2 commits into from
Nov 21, 2024

Conversation

KennthShang
Copy link
Contributor

  1. update the scripts used in phabox
  2. try to fix the diamond version

1. update the scripts used in phabox
2. try to fix the diamond version
Copy link
Contributor

coderabbitai bot commented Nov 21, 2024

📝 Walkthrough
📝 Walkthrough

Walkthrough

The pull request involves an update to the meta.yaml file for the PhaBOX package. The version number has been incremented from "2.1.5" to "2.1.6". Alongside this version change, the SHA256 checksum for the source tarball has been updated from 875124cd1568fcb706662e7f86ff7e1ef79b38944156c8c5d0b1b329d983d73a to 548c1e374fc434f12fe1be998f4a8f707403eb56e68a0c8e4f6da14dbf98a7eb. Additionally, the requirement for the diamond package has been modified from a maximum version constraint of <=0.9.14 to an exact version requirement of =0.9.14. No other modifications to the logic, structure, or content of the file have been made.

Possibly related PRs

  • bump to 2.1 and add missing requirement #51648: This PR updates the meta.yaml file for the PhaBOX package, which is directly related to the changes in the main PR that also modifies the meta.yaml file for PhaBOX, albeit with different version and dependency updates.
  • Update PhaBOX to 2.1.5 #51997: This PR also updates the meta.yaml file for the PhaBOX package, specifically changing the version and SHA256 checksum, which aligns with the version increment and checksum update in the main PR.

Suggested labels

autobump, new version


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 9b69b4f and 1690d42.

📒 Files selected for processing (1)
  • recipes/phabox/meta.yaml (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • recipes/phabox/meta.yaml

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: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between bc01cb5 and 9b69b4f.

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

10-10: Verify SHA256 checksum against upstream tarball

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

recipes/phabox/meta.yaml Show resolved Hide resolved
recipes/phabox/meta.yaml Outdated Show resolved Hide resolved
@KennthShang
Copy link
Contributor Author

KennthShang commented Nov 21, 2024

Fixed the version of the diamond.

@KennthShang
Copy link
Contributor Author

@BiocondaBot please add label

@BiocondaBot BiocondaBot added the please review & merge set to ask for merge label Nov 21, 2024
@KennthShang
Copy link
Contributor Author

@BiocondaBot please fetch artifacts

@BiocondaBot
Copy link
Collaborator

Package(s) built are ready for inspection:

Arch Package Zip File / Repodata CI Instructions
noarch phabox-2.1.6-pyhdfd78af_0.tar.bz2 noarch.zip GitHub Actions
showYou may also use conda to install after downloading and extracting the zip file. conda install -c ./packages <package name>

Docker image(s) built:

Package Tag CI Install with docker
phabox 2.1.6--pyhdfd78af_0 GitHub Actions
showImages are in the linux-64 zip file above.gzip -dc images/phabox---2.1.6--pyhdfd78af_0.tar.gz | docker load

@martin-g martin-g merged commit c2160ce into bioconda:master Nov 21, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
please review & merge set to ask for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants