Fix pgscatalog-utils patch update 1.4.2

[nebfield]

pip check was failing on the autobump

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]

@BiocondaBot please add label

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces updates to the meta.yaml file for the pgscatalog-utils package. Key changes include an increment in the version number from 1.4.1 to 1.4.2, along with an updated SHA256 checksum for the source tarball, indicating modifications to the package's contents. The build number has been adjusted from 1 to 0. Additionally, the version constraint for the pgscatalog.core dependency has been revised from >=0.3.1,<0.4.0 to >=0.3.2,<0.4.0, reflecting an increase in the required version of this dependency. All other sections of the meta.yaml file, such as the package name, source URL, build script, test commands, and metadata, remain unchanged.

Possibly related PRs

• Update pgscatalog-utils to 1.4.0 #51234: This PR updates the pgscatalog-utils package to version 1.4.0, which is directly related to the main PR that updates the same package to version 1.4.2.
• Fix pgscatalog-utils 1.4.1 #51256: This PR also updates the pgscatalog-utils package, specifically from 1.4.0 to 1.4.1, indicating a close relationship with the main PR's changes.

Suggested labels

please review & merge

Suggested reviewers

• martin-g
• AndreaGuarracino

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 05f6c3f and f914cf1.

📒 Files selected for processing (1)

• recipes/pgscatalog-utils/meta.yaml (2 hunks)

🔇 Additional comments (3)

recipes/pgscatalog-utils/meta.yaml (3)

2-2: LGTM: Version bump and checksum update look correct.

The version bump to 1.4.2 and corresponding SHA256 checksum update are properly synchronized.

Also applies to: 10-10

---

15-15: LGTM: Build number correctly reset.

Build number has been appropriately reset to 0 following the version bump.

---

27-27: Verify if this dependency update resolves the pip check failure.

The minimum version requirement for pgscatalog.core has been increased from >=0.3.1 to >=0.3.2, which should address the pip check failure mentioned in the PR description.

Let's verify if there are any other potential dependency conflicts:

✅ Verification successful

Let me check the dependencies in the related packages to verify if there are any potential conflicts.

---

The dependency update appears compatible with related packages

The verification shows that both related packages (pgscatalog.match and pgscatalog.calc) specify pgscatalog.core >=0.3.0,<0.4.0 as their dependency requirement. The updated version requirement in pgscatalog-utils (>=0.3.2,<0.4.0) is fully compatible with these constraints, as it falls within their allowed version range. This update should resolve the pip check failure without introducing new dependency conflicts.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any other potential dependency conflicts in related packages

# Look for other packages that depend on pgscatalog.core
rg -l "pgscatalog[.]core.*[0-9]" --type yaml

# Look for any other packages that might be affected by this update
rg -l "pgscatalog-utils.*[0-9]" --type yaml

Length of output: 196

---

Script:

#!/bin/bash
# Check the dependency specifications in the related packages
echo "=== pgscatalog.match dependencies ==="
cat recipes/pgscatalog.match/meta.yaml

echo -e "\n=== pgscatalog.calc dependencies ==="
cat recipes/pgscatalog.calc/meta.yaml

Length of output: 2951

---

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.