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 pgscatalog-utils to 1.4.0 #51235

Closed
wants to merge 4 commits into from

Conversation

nebfield
Copy link
Contributor

@nebfield nebfield commented Oct 8, 2024

Dependencies received a minor version bump, so need to manually update

Not sure how #51234 is passing CI/CD 🤔 pyproject.toml specifies different dependencies:

...
"pgscatalog.calc" = "^0.3.0"
"pgscatalog.core" =  "^0.3.1"
"pgscatalog.match" =  "^0.3.2"

to the meta.yaml (which is fixed in this PR)

TODO:

  • fix match dependency

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

Copy link
Contributor

coderabbitai bot commented Oct 8, 2024

📝 Walkthrough
📝 Walkthrough

Walkthrough

The changes in this pull request focus on the meta.yaml file for the pgscatalog-utils package. The version number has been updated from 1.3.1 to 1.4.0, and the SHA256 checksum for the source tarball has been modified to correspond with the new version. Additionally, the build number has been incremented from 0 to 1. The version constraints for three dependencies—pgscatalog.calc, pgscatalog.core, and pgscatalog.match—have been altered, increasing the minimum required versions for these packages. Specifically, the constraints for pgscatalog.calc have changed from >=0.2.1,<0.3.0 to >=0.3.0,<0.4.0, for pgscatalog.core from >=0.2.1,<0.3.0 to >=0.3.1,<0.4.0, and for pgscatalog.match from >=0.2.1,<0.3.0 to >=0.3.2,<0.4.0. Furthermore, a new command pip check has been added to the test section, and a new requirement for pip has been included under requires. The overall structure of the meta.yaml file remains consistent, with no changes to the build script or host requirements beyond those noted.

Possibly related PRs

Suggested labels

please review & merge, new version


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)

1-1: Minor: Consider removing the extra blank line at the beginning of the file.

While it doesn't affect functionality, removing the extra blank line at the beginning of the file would improve adherence to YAML style guidelines.

🧰 Tools
🪛 yamllint

[warning] 1-1: too many blank lines

(1 > 0) (empty-lines)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 9d020f5 and 7b03f99.

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

[warning] 1-1: too many blank lines

(1 > 0) (empty-lines)


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

(syntax)

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

3-3: Version update looks good.

The package version has been correctly updated to 1.4.0, which aligns with the PR objective.


18-18: run_exports section is correctly updated.

The pin_subpackage macro with max_pin='x.x' ensures that downstream dependencies will use a compatible version of pgscatalog-utils, allowing for minor version updates. This is a good practice for maintaining compatibility.


27-29: Dependency versions have been updated appropriately.

The minimum versions for pgscatalog.calc, pgscatalog.core, and pgscatalog.match have been increased while maintaining an upper bound at the next major version. This aligns with the PR objective and follows good versioning practices.

To ensure compatibility with the updated dependencies, please run the following script:

This script will perform a dry-run installation of each dependency to verify their availability and compatibility.


11-11: SHA256 checksum has been updated.

The SHA256 checksum has been changed to match the new version of the package. This is necessary and expected.

To verify the correctness of the SHA256 checksum, you can run the following script:

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)

1-2: Static analysis hints can be ignored.

The static analysis tool reported two issues:

  1. Too many blank lines at the beginning of the file.
  2. Syntax error with '%' character on line 2.

These can be safely ignored:

  • The blank line at the beginning doesn't affect functionality.
  • The '%' character is part of the Jinja2 templating syntax used in Conda recipes, which is correct and expected in this context.

If desired, you could remove the blank line at the beginning of the file for consistency, but it's not necessary.

🧰 Tools
🪛 yamllint

[warning] 1-1: too many blank lines

(1 > 0) (empty-lines)


[error] 2-2: 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 7b03f99 and 38584e6.

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

[warning] 1-1: too many blank lines

(1 > 0) (empty-lines)


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

(syntax)

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

3-3: Version update looks good.

The version has been correctly updated to 1.4.0, which is consistent with the PR objectives.


16-16: Build number increment is correct.

The build number has been properly incremented from 0 to 1. This is the correct practice when updating a package, as it allows for distinguishing between different builds of the same version.


37-37: Addition of 'pip check' and 'pip' requirement is beneficial.

The inclusion of the 'pip check' command in the test section and the addition of 'pip' to the test requirements are positive changes. These additions will help ensure that all dependencies are properly satisfied during the package installation and testing process.

Also applies to: 45-46


Line range hint 1-58: Overall, the changes look good and are consistent with the PR objectives.

Summary of changes:

  1. Version updated to 1.4.0
  2. SHA256 checksum updated
  3. Build number incremented
  4. Dependency versions updated
  5. 'pip check' command and 'pip' requirement added to test section

All changes follow good practices for updating a Conda recipe. The version update, dependency changes, and additional checks will help ensure the package is up-to-date and properly tested. Please make sure to verify the SHA256 checksum and run the suggested compatibility checks before merging.


27-29: Dependency version updates look appropriate.

The version constraints for pgscatalog.calc, pgscatalog.core, and pgscatalog.match have been updated to align with the new package version. The use of both lower and upper bounds is a good practice for maintaining compatibility.

To ensure these updated dependencies are compatible with the new version of pgscatalog-utils, you can run the following command:

#!/bin/bash
# Check if the updated dependencies are compatible with the new version
pip install pgscatalog-utils==1.4.0 pgscatalog.calc==0.3.0 pgscatalog.core==0.3.1 pgscatalog.match==0.3.2
pip check

This will attempt to install the package with the minimum versions of the updated dependencies and check for any compatibility issues.


11-11: SHA256 checksum has been updated.

The SHA256 checksum has been changed, which is expected when updating the package version. However, it's important to ensure that this checksum is correct for the new version's source tarball.

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

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

@nebfield nebfield closed this Oct 8, 2024
@nebfield nebfield deleted the update-pgscatalog-utils branch October 8, 2024 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant