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.core to 0.3.1 #51201

Merged
merged 2 commits into from
Oct 7, 2024

Conversation

nebfield
Copy link
Contributor

@nebfield nebfield commented Oct 7, 2024

Bump pgscatalog.core from 0.2.2 -> 0.3.1

0.3.x added pydantic as a dependency, which broke 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>.

Copy link
Contributor

coderabbitai bot commented Oct 7, 2024

📝 Walkthrough
📝 Walkthrough

Walkthrough

The pull request includes updates to the meta.yaml file for the pgscatalog.core package. The version number has been incremented from 0.2.2 to 0.3.1, and the SHA256 checksum for the source package has been updated to 612cc10afc4bea0dc5edfc6b279fc92b76e6833a9152e5bd63a7f98da4a125ad. Additionally, the version constraint for the pyliftover dependency has been modified from >=0.4.0,<0.5.0 to >=0.4.1,<0.5.0. A new dependency, pydantic >=2.9.0,<3.0.0, has been added to the requirements section. The changes primarily focus on versioning updates and the introduction of a new package requirement.

Possibly related PRs

  • Update architeuthis to 0.3.1 #50970: This PR updates the version number in the meta.yaml file for the architeuthis package, similar to the version update from 0.2.2 to 0.3.1 in the main PR for pgscatalog.core.
  • Update giatools to 0.3.1 #51007: This PR also updates the version number in the meta.yaml file for the giatools package from 0.3 to 0.3.1, paralleling the version increment in the main PR.
  • Update d4tools to 0.3.11 #51110: This PR updates the version number in the meta.yaml file for the d4tools package from 0.3.10 to 0.3.11, reflecting a similar versioning change as seen in the main PR.
  • Update protgraph to 0.3.11 #51164: This PR updates the version number in the meta.yaml file for the protgraph package from 0.3.10 to 0.3.11, which is consistent with the version update in the main PR.

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 d590c0a and 325ee2d.

📒 Files selected for processing (1)
  • recipes/pgscatalog.core/meta.yaml (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • recipes/pgscatalog.core/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: 0

🧹 Outside diff range and nitpick comments (1)
recipes/pgscatalog.core/meta.yaml (1)

Line range hint 18-18: Consider resetting the build number for the new version.

The update from version 0.2.2 to 0.3.1, along with the addition of pydantic as a dependency, represents a significant change in the package. These changes may impact users, particularly those who might need to adapt their code to work with pydantic.

Given these substantial changes, it's recommended to reset the build number to 0 for this new version. This helps to clearly differentiate it from previous builds and follows the common practice for version updates in conda recipes.

Please consider updating the build number:

-  number: 0
+  number: 0  # Reset to 0 for new version
🧰 Tools
🪛 yamllint

[error] 1-1: 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 7f3c9f8 and d590c0a.

📒 Files selected for processing (1)
  • recipes/pgscatalog.core/meta.yaml (2 hunks)
🧰 Additional context used
🔇 Additional comments (3)
recipes/pgscatalog.core/meta.yaml (3)

2-2: Version update looks good.

The version has been correctly updated from 0.2.2 to 0.3.1, which aligns with the PR objective.


10-10: SHA256 checksum updated.

The SHA256 checksum has been updated, which is consistent with the version change. However, it's important to verify that this checksum is correct for the new version of the package.

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

Compare the output with the SHA256 value in the meta.yaml file.


36-36: New dependency added: pydantic.

The addition of pydantic as a dependency is in line with the PR objectives. The version constraint (>=2.9.0,<3.0.0) is appropriate, allowing for minor updates while preventing major version changes.

To ensure this change is fully integrated:

  1. Check if the package's code has been updated to use pydantic where appropriate.
  2. Verify that any documentation or README files have been updated to reflect this new dependency.
  3. Consider running the package's test suite to ensure compatibility with pydantic.

You can use the following command to check for pydantic usage in the package code:

This will help verify that the new dependency is being utilized in the codebase.

@nebfield nebfield changed the title Bump pgscatalog.core to 0.3.1 Update pgscatalog.core to 0.3.1 Oct 7, 2024
@BiocondaBot
Copy link
Collaborator

No artifacts found on the most recent builds. Either the builds failed, the artifacts have been removed due to age, or the recipe was blacklisted/skipped.

@nebfield
Copy link
Contributor Author

nebfield commented Oct 7, 2024

@BiocondaBot please add label

@BiocondaBot BiocondaBot added the please review & merge set to ask for merge label Oct 7, 2024
@nebfield
Copy link
Contributor Author

nebfield commented Oct 7, 2024

@BiocondaBot please fetch artifacts

@BiocondaBot
Copy link
Collaborator

Package(s) built are ready for inspection:

Arch Package Zip File / Repodata CI Instructions
noarch pgscatalog.core-0.3.1-pyhdfd78af_0.tar.bz2 LinuxArtifacts.zip Azure
showYou may also use conda to install after downloading and extracting the zip file. From the LinuxArtifacts directory: conda install -c ./packages <package name>

Docker image(s) built:

Package Tag CI Install with docker
pgscatalog.core 0.3.1--pyhdfd78af_0 Azure
showImages for Azure are in the LinuxArtifacts zip file above.gzip -dc LinuxArtifacts/images/pgscatalog.core:0.3.1--pyhdfd78af_0.tar.gz | docker load

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