Update peaks2utr to 1.3.2

[BiocondaBot]

Update peaks2utr: 1.3.0 → 1.3.2

Info	Link or Description
Recipe	recipes/peaks2utr (click to view/edit other files)
Summary	A robust, parallelized Python CLI for annotating three_prime_UTR
Home	https://github.com/haessar/peaks2utr
Releases	https://pypi.org/pypi/peaks2utr/json

---

This pull request was automatically generated (see docs).

Summary by CodeRabbit

• New Features
  • Updated the peaks2utr package to version 1.3.2, enhancing functionality and performance.
  • New source URL for the package tarball to reflect the updated version.
• Bug Fixes
  • Updated SHA256 checksum for the source tarball to ensure integrity and security.

[coderabbitai]

Walkthrough

The pull request updates the peaks2utr package by changing its version from "1.3.0" to "1.3.2". This includes modifications to the SHA256 checksum and the source URL to align with the new version. The build number remains unchanged.

Changes

Files	Change Summary
recipes/peaks2utr/meta.yaml	- Version updated from "1.3.0" to "1.3.2". - SHA256 checksum updated. - Source URL updated to point to the new version's tarball.

Poem

In the garden of code, a new version blooms,
From "one point three" to "two", it zooms!
With checksums adjusted and URLs bright,
The peaks2utr hops into the light.
A leap for the package, a joyful cheer,
CodeRabbit sings, "The update is here!" 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between d6403ea and b7b88c1.

📒 Files selected for processing (1)

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

🔇 Additional comments (3)

recipes/peaks2utr/meta.yaml (3)

2-2: Version update looks good.

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

---

9-9: URL and other aspects of the recipe look good.

The URL has been correctly updated to reflect the new version (1.3.2) due to the Jinja2 templating. As this is a minor version update, it's reasonable that no other changes to build instructions or dependencies were required. However, it might be worth double-checking if any new dependencies were introduced in this version update.

To verify if any new dependencies were introduced, you can run:

#!/bin/bash
# Description: Compare dependencies between versions 1.3.0 and 1.3.2

# Download both versions
curl -sL https://pypi.io/packages/source/p/peaks2utr/peaks2utr-1.3.0.tar.gz -o peaks2utr-1.3.0.tar.gz
curl -sL https://pypi.io/packages/source/p/peaks2utr/peaks2utr-1.3.2.tar.gz -o peaks2utr-1.3.2.tar.gz

# Extract and compare setup.py or pyproject.toml files
tar -xzf peaks2utr-1.3.0.tar.gz
tar -xzf peaks2utr-1.3.2.tar.gz

echo "Differences in setup.py or pyproject.toml:"
diff -u peaks2utr-1.3.0/setup.py peaks2utr-1.3.2/setup.py || \
diff -u peaks2utr-1.3.0/pyproject.toml peaks2utr-1.3.2/pyproject.toml

# Clean up
rm -rf peaks2utr-1.3.0 peaks2utr-1.3.1 peaks2utr-1.3.0.tar.gz peaks2utr-1.3.2.tar.gz

This script will show any differences in dependencies between the two versions. If there are no differences, no output will be produced.

---

10-10: Verify the SHA256 checksum.

The SHA256 checksum has been updated, which is necessary when changing the package version. However, we should verify that this checksum is correct for the new version 1.3.2 of peaks2utr.

Run the following script to verify the SHA256 checksum:

If the script output shows "OK", then the SHA256 checksum is correct.

---

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.