Update galaxy-data to 24.1.3

[BiocondaBot]

Update galaxy-data: 24.1.2 → 24.1.3

Info	Link or Description
Recipe	recipes/galaxy-data (click to view/edit other files)
Summary	The Galaxy models, datatype framework, and datatype implementations.
Home	https://galaxyproject.org
Releases	https://pypi.org/pypi/galaxy_data/json
Recipe Maintainer(s)	@bernt-matthias

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces updates to the meta.yaml file for the galaxy-data package. The version number has been incremented from "24.1.2" to "24.1.3", and the SHA256 checksum has been updated to reflect this new version. Specifically, the checksum changed from "d75e5e9e954773c683cb54a655da0c9733f1c6b0f6e691fedb6a1edc6e4aede2" to "e5f32420a9fd33ea4fb896dcbbbb754a4be23f39c48d3a196aac2bde1d70d53a". Additionally, the setuptools package has been added to the host requirements, indicating a new dependency necessary for building the package. The remainder of the meta.yaml structure, including the source URL, build script, and other requirements, has not been modified, and there are no changes to the entry points or test imports, indicating that the functionality and behavior of the package remain consistent aside from the version and checksum updates.

Possibly related PRs

• Update galaxy-schema to 24.1.3 #51756: The changes in this PR involve updating the galaxy-schema package's version and SHA256 checksum, as well as adding setuptools as a dependency, which directly relates to the changes made in the main PR for the galaxy-data package.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between f83e9c7 and 7ad1993.

📒 Files selected for processing (1)

• recipes/galaxy-data/meta.yaml (2 hunks)

🧰 Additional context used

🪛 yamllint

recipes/galaxy-data/meta.yaml

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

(syntax)

🔇 Additional comments (3)

recipes/galaxy-data/meta.yaml (3)

29-29: LGTM: Addition of setuptools as build dependency

The addition of setuptools to host requirements is appropriate and follows conda-forge packaging best practices.

---

Line range hint 1-93: LGTM: Well-structured recipe update

The recipe update is clean and well-structured:

• Version bump follows semantic versioning
• Dependencies are properly pinned
• Test suite remains comprehensive
• Metadata is well-maintained

---

1-2: Verify package integrity

The version bump and checksum update appear correct. Let's verify the SHA256 checksum matches the PyPI package.

🧰 Tools

🪛 yamllint

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

(syntax)

---

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.