Update phyloacc to 2.4.2

[BiocondaBot]

Update phyloacc: 2.4.1 → 2.4.2

Info	Link or Description
Recipe	recipes/phyloacc (click to view/edit other files)
Summary	Bayesian estimation of substitution rate shifts in non-coding regions
Home	https://phyloacc.github.io/
Releases	https://github.com/phyloacc/PhyloAcc/tags
Recipe Maintainer(s)	@gwct
Author	@phyloacc

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces updates to the meta.yaml file for the PhyloAcc package. The version number has been incremented from 2.4.1 to 2.4.2, and the SHA256 checksum has been updated from 919203dc541c172f9e835b0568f6abd49999a24734957fec020b01161479282c to effa443400fa1ebfa43de1daf551c8344f883bcf8d048a11e64fca64243a93fe. Additionally, the build number has been reset from 2 to 0. The skip directive remains unchanged, indicating that builds for Python versions less than 3.11 should continue to be skipped. The requirements for both build and run environments have not been altered, and the test section still includes the wget requirement without any changes. The about section, which contains URLs and licensing information, also remains intact. The primary focus of the changes is on versioning, checksum updates, and the reset of the build number.

Possibly related PRs

• Update phyloacc to 2.4.1 #51082: Updates the PhyloAcc package from version 2.4.0 to 2.4.1, directly preceding the current update to 2.4.2.
• Update phyloacc to 2.4.0 #50992: Updates the PhyloAcc package from version 2.3.4 to 2.4.0, contributing to the versioning progression that leads to the current PR.
• Update PhyloAcc recipe #51090: Modifies the PhyloAcc package by changing the build number and updating dependencies, relevant to the ongoing maintenance reflected in the main PR.
• Update PhyloAcc recipe #51224: Enhances the testing framework for the PhyloAcc package, indicating related improvements and updates relevant to the changes made 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 b072084 and 7d9b5ae.

📒 Files selected for processing (1)

• recipes/phyloacc/meta.yaml (2 hunks)

🧰 Additional context used

🔇 Additional comments (4)

recipes/phyloacc/meta.yaml (4)

2-2: Version update looks good.

The version has been correctly updated from 2.4.1 to 2.4.2, which aligns with the PR objectives.

---

14-14: Build number reset is correct.

The build number has been appropriately reset to 0 for the new version 2.4.2. This is the correct practice when updating to a new version of the package.

---

Line range hint 1-65: Overall changes look good and follow best practices.

The updates to the meta.yaml file are consistent with a standard version bump for a Conda package:

1. The version has been incremented from 2.4.1 to 2.4.2.
2. The SHA256 checksum has been updated accordingly.
3. The build number has been reset to 0 for the new version.

These changes align with the PR objectives and follow best practices for package management in Conda. No unexpected modifications were found in the rest of the file.

---

3-3: SHA256 checksum has been updated.

The SHA256 checksum has been changed, which is expected with a new version. However, it's important to verify that this checksum corresponds to the correct source file for version 2.4.2.

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

---

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.