Update peaks2utr to 1.3.3

[BiocondaBot]

Update peaks2utr: 1.3.2 → 1.3.3

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

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces an update to the meta.yaml file for the peaks2utr package. The version number has been changed from 1.3.2 to 1.3.3, indicating a new release of the package. Alongside this version increment, the SHA256 checksum for the source package has been modified from ddf7c44725124aabcc4541e567f493de9658b2036a0a804d997376a7bf6b0828 to 5fab611d8039a210936f172ccf6fb90989c91e53fb8ea8b18026cbce8a35d9b7. No other modifications have been made to the structure or content of the meta.yaml file.

Possibly related PRs

• Update peaks2utr to 1.3.2 #50979: This PR updates the peaks2utr package from version 1.3.0 to 1.3.2, which is directly related to the main PR that updates the version from 1.3.2 to 1.3.3. Both PRs involve changes to the same meta.yaml file for the peaks2utr package, specifically regarding version and SHA256 checksum updates.

Suggested reviewers

• martin-g

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 716ea83 and 97d81a2.

📒 Files selected for processing (1)

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

🔇 Additional comments (3)

recipes/peaks2utr/meta.yaml (3)

2-2: Version number update looks good.

The version number has been correctly updated from 1.3.2 to 1.3.3, which aligns with the PR objectives.

---

Line range hint 1-55: Overall update looks good, consider checking for new features or dependencies.

The version bump and checksum update are the only changes in this file, which is consistent with an automated version bump process. The build number remains at 0, which is correct for a new version. However, it might be worth manually checking if version 1.3.3 introduces any new features or dependencies that should be reflected in this recipe.

To assist with this verification, you can run the following script to check for any significant changes between versions 1.3.2 and 1.3.3:

#!/bin/bash
# Description: Check for significant changes between peaks2utr versions 1.3.2 and 1.3.3

# Test: Compare the setup.py files of both versions
wget https://raw.githubusercontent.com/haessar/peaks2utr/v1.3.2/setup.py -O setup_1.3.2.py
wget https://raw.githubusercontent.com/haessar/peaks2utr/v1.3.3/setup.py -O setup_1.3.3.py
diff -u setup_1.3.2.py setup_1.3.3.py

# Test: Check for changes in requirements
grep -E "install_requires|extras_require" setup_1.3.3.py

# Test: Check for any new scripts or entry points
grep -E "scripts|entry_points" setup_1.3.3.py

🧰 Tools

🪛 yamllint

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

(syntax)

---

10-10: Verify the SHA256 checksum.

The SHA256 checksum has been updated, which is expected with a new version. However, we should verify that this checksum is correct for version 1.3.3 of the package.

Run the following script to verify the SHA256 checksum:

---

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.