Update dxpy to 0.383.1

[BiocondaBot]

Update dxpy: 0.382.0 → 0.383.1

Info	Link or Description
Recipe	recipes/dxpy (click to view/edit other files)
Summary	DNAnexus Platform API bindings for Python
Home	https://github.com/dnanexus/dx-toolkit
Releases	https://pypi.org/pypi/dxpy/json
Recipe Maintainer(s)	@notestaff

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates the meta.yaml file for the dxpy package. The version number is changed from "0.382.0" to "0.383.1", and the SHA256 checksum for the source tarball is updated accordingly. Additionally, the source URL is modified to reflect the new version.

Changes

File	Change Summary
recipes/dxpy/meta.yaml	- Version updated from "0.382.0" to "0.383.1"
	- SHA256 checksum updated from c8427fdc2d293622e2fa250afe6e51fc85a21c5abed697be863eb7a644c502e7 to 377af4014a5f27efd6fe9478d0fa9c30ced245947fbd2e2e5713c8a37db598b0
	- Source URL adjusted to reflect the new version

Possibly related PRs

• Update architeuthis to 0.3.1 #50970: This PR involves updating the version number and SHA256 checksum in the meta.yaml file, similar to the updates made in the main PR for the dxpy package.
• Update peaks2utr to 1.3.2 #50979: This PR also updates the version number and SHA256 checksum in the meta.yaml file, reflecting a similar type of change as seen in the main PR.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 67be0ec and aa5ddfa.

📒 Files selected for processing (1)

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

🔇 Additional comments (3)

recipes/dxpy/meta.yaml (3)

2-2: Version update looks good.

The version has been correctly updated to 0.383.1, which aligns with the PR objective.

---

10-10: SHA256 checksum has been updated.

The SHA256 checksum has been updated, which is necessary for the new version. However, it's important to verify that this checksum corresponds to the correct source package for version 0.383.1.

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

#!/bin/bash
# Description: Verify the SHA256 checksum of the dxpy source package

# Download the package
curl -sL https://pypi.io/packages/source/d/dxpy/dxpy-0.383.1.tar.gz -o dxpy-0.383.1.tar.gz

# Calculate and compare the SHA256 checksum
echo "377af4014a5f27efd6fe9478d0fa9c30ced245947fbd2e2e5713c8a37db598b0 dxpy-0.383.1.tar.gz" | sha256sum --check

# Clean up
rm dxpy-0.383.1.tar.gz

This script will download the package, calculate its SHA256 checksum, and compare it with the one provided in the meta.yaml file. If the check passes, it confirms that the checksum is correct for the given version.

---

Line range hint 1-73: Consider verifying dependencies for the new version.

While the version update appears to be minor (0.382.0 to 0.383.1), it's worth verifying if any dependencies need to be updated. The current recipe doesn't show any changes to dependencies, but it's good practice to check the package's release notes or documentation for any new or updated requirements.

You can check the package's release notes or requirements file with the following command:

This script will clone the dx-toolkit repository, checkout the new version, and attempt to find and display the dependencies. Please review the output to ensure no new dependencies are required for this version.

✅ Verification successful

Dependencies have been verified and are up to date within setup.py. No changes are required in meta.yaml.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

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

# Clone the dx-toolkit repository
git clone https://github.com/dnanexus/dx-toolkit.git
cd dx-toolkit

# Checkout the tag for the new version
git checkout v0.383.1

# Check for a requirements file or setup.py
if [ -f "requirements.txt" ]; then
  echo "Contents of requirements.txt:"
  cat requirements.txt
elif [ -f "setup.py" ]; then
  echo "Dependencies from setup.py:"
  grep "install_requires" setup.py -A 20
else
  echo "No requirements.txt or setup.py found. Please check the documentation for dependency information."
fi

# Clean up
cd ..
rm -rf dx-toolkit

Length of output: 528

---

Script:

#!/bin/bash
# Description: Prepare repository and list tags and dependency files

# Remove existing dx-toolkit directory if it exists
if [ -d "dx-toolkit" ]; then
  echo "Removing existing dx-toolkit directory..."
  rm -rf dx-toolkit
fi

# Clone the dx-toolkit repository
git clone https://github.com/dnanexus/dx-toolkit.git
cd dx-toolkit || exit 1

# List all available tags
echo "Available tags:"
git tag -l

# Search for dependency management files
echo "Checking for dependency management files..."
if [ -f "pyproject.toml" ]; then
  echo "Found pyproject.toml:"
  cat pyproject.toml
elif [ -f "Pipfile" ]; then
  echo "Found Pipfile:"
  cat Pipfile
else
  echo "No common dependency management files found."
fi

# Clean up
cd ..

Length of output: 6457

---

Script:

#!/bin/bash
# Description: Search for dependency declarations in the dx-toolkit repository

# Clone the dx-toolkit repository if not already cloned
if [ ! -d "dx-toolkit" ]; then
  git clone https://github.com/dnanexus/dx-toolkit.git
fi
cd dx-toolkit || exit 1

# Checkout the specific tag
git checkout v0.383.1

# Use ripgrep to search for dependency-related keywords
echo "Searching for dependency declarations..."
rg --ignore-case "install_requires|dependencies|requires|setup\("

# Clean up
cd ..

Length of output: 23665

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

[BiocondaBot]

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.

[BiocondaBot]

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.