Update gseapy to 1.1.4

[BiocondaBot]

Update gseapy: 1.1.3 → 1.1.4

Info	Link or Description
Recipe	recipes/gseapy (click to view/edit other files)
Summary	Gene Set Enrichment Analysis in Python
Home	https://github.com/zqfang/gseapy
Releases	https://pypi.org/pypi/gseapy/json

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request involves an update to the meta.yaml file for the gseapy package. The version number has been changed from "1.1.3" to "1.1.4". Additionally, the source URL has been updated to reflect the new version's tarball, and the SHA256 checksum has been modified accordingly to match the new package version. The build number has been decremented from 1 to 0. The requirements section, which lists the dependencies for build, host, and run, remains unchanged. The test and about sections of the meta.yaml file also remain intact, with no modifications made to their content.

Possibly related PRs

• Update sizemeup to 1.2.3 #51114: Updates the meta.yaml file for the sizemeup package, including a version bump and SHA256 checksum update.
• Update bactopia-py to 1.2.0 #51154: Modifies the meta.yaml file for the bactopia-py package with a version increment and SHA256 checksum update.
• Update cosigt to version 0.1.3 #51540: Changes the meta.yaml file for the cosigt package, including a version change and SHA256 checksum update.
• Update pybiolib to 1.2.205 #51549: Updates the meta.yaml file for the pybiolib package with a version increment and SHA256 checksum update.
• Update crabs to 1.0.4 #51645: Modifies the meta.yaml file for the crabs package with a version change and SHA256 checksum update.
• Update gfastats to 1.3.9 #51948: Updates the meta.yaml file for the gfastats package with a version increment and SHA256 checksum update.
• Update gnparser to 1.11.0 #52046: Changes the meta.yaml file for the gnparser package with a version change and SHA256 checksum update.
• Update gnparser to 1.11.1 #52063: Updates the meta.yaml file for the gnparser package again with a version increment and SHA256 checksum update.

Suggested reviewers

• rpetit3

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 2c168fe and 51776f6.

📒 Files selected for processing (1)

• recipes/gseapy/meta.yaml (1 hunks)

🔇 Additional comments (3)

recipes/gseapy/meta.yaml (3)

15-15: LGTM: Build number reset

Correctly reset build number to 0 for the new version, following Conda packaging best practices.

---

Line range hint 17-31: Verify dependency requirements for new version

Let's ensure the requirements remain accurate for version 1.1.4.

#!/bin/bash
# Description: Check for any dependency changes in the new version

# Get package metadata from PyPI
curl -s "https://pypi.org/pypi/gseapy/1.1.4/json" | jq -r '.info.requires_dist'

# Check setup.py/pyproject.toml in the source distribution for requirements
curl -sL "https://files.pythonhosted.org/packages/12/92/0a4e24f4a0ac772e8ec652f299a89292eb66d67e329579e1ea48cc006250/gseapy-1.1.4.tar.gz" | tar -xz --to-stdout "*/setup.py" "*/pyproject.toml" 2>/dev/null || true

🧰 Tools

🪛 yamllint

[error] 18-18: trailing spaces

(trailing-spaces)

---

3-3: Verify package source integrity

The version update, URL, and checksum changes are consistent with the PR objectives.

Let's verify the package source integrity:

Also applies to: 6-7

✅ Verification successful

Package source integrity verified successfully

The verification confirms:

• URL in meta.yaml matches PyPI's source distribution URL
• SHA256 checksum in meta.yaml (7e858752d7684b1abed124c585f3ca2f156ff22985575234232a54c57b88ba66) matches PyPI's SHA256 digest
• Version 1.1.4 exists on PyPI with the correct source distribution

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the source URL and checksum for gseapy 1.1.4

# Download the package and compute its checksum
curl -sL "https://files.pythonhosted.org/packages/12/92/0a4e24f4a0ac772e8ec652f299a89292eb66d67e329579e1ea48cc006250/gseapy-1.1.4.tar.gz" | sha256sum

# Verify the package exists on PyPI and check its metadata
curl -s "https://pypi.org/pypi/gseapy/1.1.4/json" | jq -r '.urls[] | select(.packagetype=="sdist") | {url, digests}'

Length of output: 356

---

Script:

#!/bin/bash
# Let's verify the package details from the meta.yaml file and compare with PyPI
echo "=== Content of meta.yaml ==="
cat recipes/gseapy/meta.yaml

echo -e "\n=== PyPI package verification ==="
# Verify package existence and get SHA256
curl -s "https://pypi.org/pypi/gseapy/1.1.4/json" | \
  jq -r '.urls[] | select(.packagetype=="sdist") | {url, digests}'

Length of output: 1744

---

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.