Update phyloacc to 2.4.0

[BiocondaBot]

Update phyloacc: 2.3.4 → 2.4.0

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 updates the meta.yaml file for the PhyloAcc package, incrementing the version number from "2.3.4" to "2.4.0" and updating the SHA256 checksum to correspond with the new version's source code. The build number is reset from 2 to 0, and the build is configured to skip for Python versions less than 3.8. The run exports remain unchanged, maintaining the pinning of the subpackage phyloacc.

Changes

File	Change Summary
recipes/phyloacc/meta.yaml	- Version updated from "2.3.4" to "2.4.0" - SHA256 updated from "a31fe266..." to "3f5cea90..." - Build number reset from 2 to 0 - Build marked to skip for Python < 3.8 - Run exports unchanged

Possibly related PRs

• Update architeuthis to 0.3.1 #50970: Updates the version number and SHA256 checksum in the meta.yaml file, similar to the main PR for PhyloAcc.
• Update stranger to 0.9.2 #50971: Also updates the version number and SHA256 checksum in the meta.yaml file, paralleling the changes made in the main PR.
• Update vsearch to 2.29.0 #50975: Updates the version number and SHA256 checksum in the meta.yaml file, indicating a new release.
• Update peaks2utr to 1.3.2 #50979: Reflects an update to the version number and SHA256 checksum in the meta.yaml file, aligning with 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 67be0ec and 4ffbe68.

📒 Files selected for processing (1)

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

🔇 Additional comments (4)

recipes/phyloacc/meta.yaml (4)

2-2: Version update looks good.

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

---

14-14: Build number reset is correct.

The build number has been appropriately reset to 0 for the new version, which is the expected practice when updating to a new package version.

---

Line range hint 1-67: Verify dependencies and metadata for the new version.

While the version update looks good, it's important to ensure that:

1. All dependencies are still compatible with the new version.
2. No new dependencies are required for version 2.4.0.
3. The package metadata (license, description, etc.) is still accurate.

Please double-check these aspects to ensure the recipe is fully up-to-date.

To assist with this verification, you can run the following script:

This script will show any differences in dependencies and metadata between the old and new versions. Please review the output to ensure all changes are intentional and necessary for the new version.

✅ Verification successful

To resolve the issues encountered with the previous script, please run the following updated script to accurately compare dependencies and metadata between versions:

---

Dependencies and metadata verified successfully. No changes detected.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any changes in dependencies or metadata between versions

# Fetch the previous version's meta.yaml
curl -sL https://raw.githubusercontent.com/bioconda/bioconda-recipes/master/recipes/phyloacc/meta.yaml > old_meta.yaml

# Compare dependencies
echo "Comparing dependencies:"
diff -u <(grep -A20 "requirements:" old_meta.yaml | grep -v "^--") <(grep -A20 "requirements:" recipes/phyloacc/meta.yaml | grep -v "^--")

# Compare metadata
echo "Comparing metadata:"
diff -u <(grep -A10 "about:" old_meta.yaml | grep -v "^--") <(grep -A10 "about:" recipes/phyloacc/meta.yaml | grep -v "^--")

# Clean up
rm old_meta.yaml

Length of output: 713

---

Script:

# 
#!/bin/bash
# Description: Check for any changes in dependencies or metadata between versions without using process substitution

# Fetch the previous version's meta.yaml
curl -sL https://raw.githubusercontent.com/bioconda/bioconda-recipes/master/recipes/phyloacc/meta.yaml -o old_meta.yaml

# Extract and save the requirements section from the old meta.yaml
grep -A20 "requirements:" old_meta.yaml | grep -v "^--" > old_requirements.txt

# Extract and save the about section from the old meta.yaml
grep -A10 "about:" old_meta.yaml | grep -v "^--" > old_about.txt

# Extract and save the requirements section from the new meta.yaml
grep -A20 "requirements:" recipes/phyloacc/meta.yaml | grep -v "^--" > new_requirements.txt

# Extract and save the about section from the new meta.yaml
grep -A10 "about:" recipes/phyloacc/meta.yaml | grep -v "^--" > new_about.txt

# Compare dependencies
echo "Comparing dependencies:"
diff -u old_requirements.txt new_requirements.txt

# Compare metadata
echo "Comparing metadata:"
diff -u old_about.txt new_about.txt

# Clean up temporary files
rm old_meta.yaml old_requirements.txt old_about.txt new_requirements.txt new_about.txt

Length of output: 642

---

3-3: Verify the SHA256 checksum.

The SHA256 checksum has been updated. It's important to ensure this checksum matches the official release.

Run the following script to verify the 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.

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

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