Update pgscatalog.calc to 0.3.0

[nebfield]

Autobump broke because pgscatalog.core needs a minor version bump

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

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces updates to the meta.yaml file for the pgscatalog.calc package. The package version has been incremented from 0.2.2 to 0.3.0, and the SHA256 checksum for the source tarball has been updated accordingly. The requirements section has been modified to specify a new version range for the pgscatalog.core dependency, now requiring a version greater than or equal to 0.3.0 and less than 0.4.0. Other dependencies listed in the file, such as numpy, pandas, pyarrow, scikit-learn, and scipy, have not had their version constraints changed. The primary focus of the changes is on updating the package version, adjusting the checksum, and modifying the dependency specification for pgscatalog.core.

Possibly related PRs

• Update pgscatalog.core to 0.3.1 #51201: This PR updates the pgscatalog.core package to version 0.3.1, which is directly related to the main PR's update of the pgscatalog.calc package to require pgscatalog.core >=0.3.0,<0.4.0.
• Update pgscatalog.match to 0.3.2 #51216: This PR updates the pgscatalog.match package to version 0.3.2, which is part of the same pgscatalog ecosystem and may be affected by the changes in the main PR regarding version dependencies.

Suggested labels

autobump, new version

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 308c48d and 73d11de.

📒 Files selected for processing (1)

• recipes/pgscatalog.calc/meta.yaml (2 hunks)

🧰 Additional context used

🔇 Additional comments (4)

recipes/pgscatalog.calc/meta.yaml (4)

2-2: Version update looks good.

The version bump from 0.2.2 to 0.3.0 is consistent with the PR objectives and follows semantic versioning principles for a minor version update.

---

Line range hint 1-54: Overall changes look good, PR approved pending verifications.

The changes in this PR are focused and align well with the stated objectives:

1. The package version has been updated to 0.3.0.
2. The SHA256 checksum has been updated accordingly.
3. The pgscatalog.core dependency has been updated to >=0.3.0,<0.4.0.

These changes appear to address the issue with the autobump process and the need for a minor version bump in the pgscatalog.core component. The rest of the file remains unchanged and in good order.

Please ensure that the verification steps for the SHA256 checksum and pgscatalog.core version compatibility are completed successfully before merging.

🧰 Tools

🪛 yamllint

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

(syntax)

---

29-29: Dependency update looks good, but verify compatibility.

The update of pgscatalog.core to >=0.3.0,<0.4.0 aligns with the PR objectives and follows good versioning practices. However, it's important to verify compatibility with other dependencies and check if this is the latest available version.

Run the following script to verify the pgscatalog.core version compatibility:

#!/bin/bash
# Description: Verify pgscatalog.core version compatibility

# Check the latest version of pgscatalog.core on PyPI
latest_version=$(curl -s https://pypi.org/pypi/pgscatalog.core/json | jq -r '.info.version')

echo "Latest pgscatalog.core version on PyPI: $latest_version"

# Check if the latest version is compatible with the specified range
if [[ $(echo $latest_version | cut -d. -f1-2) == "0.3" ]]; then
    echo "The specified version range (>=0.3.0,<0.4.0) includes the latest version."
else
    echo "Warning: The latest version may not be compatible with the specified range."
fi

# List other dependencies that might be affected by this change
echo "Dependencies that might be affected by pgscatalog.core version change:"
grep -A 10 'requirements:' recipes/pgscatalog.calc/meta.yaml | grep -v '^ *$' | tail -n +2

---

10-10: Verify the updated SHA256 checksum.

The SHA256 checksum has been updated, which is expected with a new version. However, it's crucial to ensure this checksum corresponds to the correct source package.

Run the following script to verify the SHA256 checksum:

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[nebfield]

@BiocondaBot please add label