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

Fix pgscatalog-utils 1.4.1 #51256

Merged
merged 5 commits into from
Oct 9, 2024
Merged

Conversation

nebfield
Copy link
Contributor

@nebfield nebfield commented Oct 8, 2024

#51254 accidentally has some dodgy dependencies 👀

Manual update to add pip check and bump minor versions

Bot commands for PR management

Please use the following BiocondaBot commands:

Everyone has access to the following BiocondaBot commands, which can be given in a comment:

@BiocondaBot please update Merge the master branch into a PR.
@BiocondaBot please add label Add the please review & merge label.
@BiocondaBot please fetch artifacts Post links to CI-built packages/containers.
You can use this to test packages locally.

Note that the @BiocondaBot please merge command is now depreciated. Please just squash and merge instead.

Also, the bot watches for comments from non-members that include @bioconda/<team> and will automatically re-post them to notify the addressed <team>.

@nebfield nebfield changed the title fix dependencies Update pgscatalog-utils to 1.4.1 Oct 8, 2024
Copy link
Contributor

coderabbitai bot commented Oct 8, 2024

📝 Walkthrough
📝 Walkthrough

Walkthrough

The pull request introduces updates to the meta.yaml file for the pgscatalog-utils package. The version number is incremented from 1.4.0 to 1.4.1, and the SHA256 checksum for the source tarball is updated to match the new version. The build number has been changed from 0 to 1. The requirements section has been modified to reflect changes in dependencies for the run environment, with the versions of pgscatalog.calc, pgscatalog.core, and pgscatalog.match updated to >=0.3.0,<0.4.0, >=0.3.1,<0.4.0, and >=0.3.3,<0.4.0, respectively. Additionally, a new requirement for pip has been added under the test section, which now includes a pip check command to ensure that package dependencies are correctly resolved. These changes collectively enhance the versioning and dependency specifications of the pgscatalog-utils package.

Possibly related PRs

  • Update pgscatalog.calc to 0.3.0 #51222: This PR updates the pgscatalog.calc package to require pgscatalog.core version >=0.3.0,<0.4.0, which aligns with the main PR's updates to the pgscatalog-utils package that also requires pgscatalog.core version >=0.3.1,<0.4.0.
  • Update pgscatalog.core to 0.3.1 #51201: This PR updates the pgscatalog.core package to version 0.3.1, which is a direct dependency of the pgscatalog-utils package as noted in the main PR.
  • Update pgscatalog.match to 0.3.2 #51216: This PR updates the pgscatalog.match package to version 0.3.2, which is also a dependency for the pgscatalog-utils package in the main PR, reflecting the same versioning requirements.
  • Update pgscatalog.match to 0.3.3 #51242: This PR updates the pgscatalog.match package to version 0.3.3, which is relevant as it continues the versioning updates for dependencies required by the pgscatalog-utils package in the main PR.
  • Update pyliftover to 0.4.1 #51205: This PR updates the pyliftover package to version 0.4.1, which is relevant as it is a new dependency added in the main PR's updates to the pgscatalog-utils package.

Suggested labels

please review & merge


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

37-37: Minor: Remove trailing spaces.

There are trailing spaces on this line. While they don't affect functionality, removing them improves code cleanliness.

You can remove the trailing spaces to resolve this minor formatting issue.

🧰 Tools
🪛 yamllint

[error] 37-37: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 77e9015 and 2d4321c.

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

[error] 37-37: trailing spaces

(trailing-spaces)

🔇 Additional comments (5)
recipes/pgscatalog-utils/meta.yaml (5)

2-2: Version update looks good.

The package version has been correctly updated from 1.4.0 to 1.4.1, which aligns with the PR title and summary.


44-45: Addition of pip to test requirements is beneficial.

Adding pip to the test requirements is a good practice. It enables the use of pip check during testing, which can help identify potential dependency issues.


36-36: Addition of pip check command is beneficial.

The inclusion of the pip check command in the test section is a good practice. It helps ensure that all package dependencies are correctly satisfied and can catch potential issues early.


26-28: Dependencies updated to newer versions.

The dependencies for pgscatalog.calc, pgscatalog.core, and pgscatalog.match have been updated to newer versions. This change appears to be in line with the package update.

To ensure compatibility, please verify that these updated dependencies are indeed required for pgscatalog-utils 1.4.1. You can check this by running:

#!/bin/bash
# Fetch the setup.py or pyproject.toml file to verify dependencies
curl -sL https://pypi.io/packages/source/p/pgscatalog-utils/pgscatalog_utils-1.4.1.tar.gz | tar -xzO '*/setup.py' '*/pyproject.toml' 2>/dev/null | grep -E "pgscatalog\.(calc|core|match)"

Compare the output with the dependencies specified in the meta.yaml file.


10-10: SHA256 checksum updated.

The SHA256 checksum has been updated, which is necessary for the new version. However, it's crucial to verify that this checksum is correct for the new source package.

To verify the SHA256 checksum, you can run the following command:

Compare the output with the SHA256 in the meta.yaml file to ensure they match.

@nebfield nebfield changed the title Update pgscatalog-utils to 1.4.1 Fix pgscatalog-utils 1.4.1 Oct 9, 2024
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/pgscatalog-utils/meta.yaml (1)

37-37: Minor formatting issues detected.

There are two minor formatting issues in the file:

  1. Trailing spaces on line 37
  2. Extra blank line at the end of the file (line 58)

While these don't affect functionality, addressing them would improve code consistency.

You can fix these issues by applying the following changes:

  1. Remove the trailing spaces after the command on line 37.
  2. Remove the extra blank line at the end of the file (line 58).

Also applies to: 58-58

🧰 Tools
🪛 yamllint

[error] 37-37: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 2d4321c and 722c91e.

📒 Files selected for processing (1)
  • recipes/pgscatalog-utils/meta.yaml (3 hunks)
🧰 Additional context used
🪛 yamllint
recipes/pgscatalog-utils/meta.yaml

[error] 37-37: trailing spaces

(trailing-spaces)


[warning] 58-58: too many blank lines

(1 > 0) (empty-lines)

🔇 Additional comments (5)
recipes/pgscatalog-utils/meta.yaml (5)

Line range hint 2-2: Version and checksum update looks good.

The version has been correctly updated to 1.4.1, and the SHA256 checksum has been updated accordingly. This is consistent with the PR objectives of updating pgscatalog-utils to version 1.4.1.

Also applies to: 11-11


15-15: Build number increment is correct.

The build number has been incremented from 0 to 1, which is the correct practice when updating a package version. This ensures that the new build is recognized as a distinct version by the Conda package manager.


36-36: Addition of pip check is a good practice.

The addition of pip to the test requirements and the inclusion of the pip check command in the test section are excellent improvements. This will help ensure that all dependencies are correctly installed and compatible, potentially catching issues early in the build process.

Also applies to: 44-45


57-57: New maintainer added successfully.

The addition of 'smlmbrt' as a new maintainer is a positive step for the project. This will help in sharing the maintenance responsibilities and potentially improve the overall management of the package.


26-28: Dependency updates look good, but verify compatibility.

The version ranges for pgscatalog.calc, pgscatalog.core, and pgscatalog.match have been updated appropriately. The new constraints (>=0.3.0,<0.4.0, >=0.3.1,<0.4.0, and >=0.3.3,<0.4.0 respectively) follow best practices by specifying both lower and upper bounds.

To ensure these updates don't introduce compatibility issues, please run the following command:

This script creates a test environment with the minimum versions of the updated dependencies and attempts to import them. If successful, it suggests that the updates are compatible.

@nebfield
Copy link
Contributor Author

nebfield commented Oct 9, 2024

@BiocondaBot please add label

@BiocondaBot BiocondaBot added the please review & merge set to ask for merge label Oct 9, 2024
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