Rebuild funannotate recipe

[mencian]

Describe your pull request here

---

Please read the guidelines for Bioconda recipes before opening a pull request (PR).

General instructions

• If this PR adds or updates a recipe, use "Add" or "Update" appropriately as the first word in its title.
• New recipes not directly relevant to the biological sciences need to be submitted to the conda-forge channel instead of Bioconda.
• PRs require reviews prior to being merged. Once your PR is passing tests and ready to be merged, please issue the @BiocondaBot please add label command.
• Please post questions on Gitter or ping @bioconda/core in a comment.

Instructions for avoiding API, ABI, and CLI breakage issues

Conda is able to record and lock (a.k.a. pin) dependency versions used at build time of other recipes.
This way, one can avoid that expectations of a downstream recipe with regards to API, ABI, or CLI are violated by later changes in the recipe.
If not already present in the meta.yaml, make sure to specify run_exports (see here for the rationale and comprehensive explanation).
Add a run_exports section like this:

build:
  run_exports:
    - ...

with ... being one of:

Case	run_exports statement
semantic versioning	{{ pin_subpackage("myrecipe", max_pin="x") }}
semantic versioning (0.x.x)	{{ pin_subpackage("myrecipe", max_pin="x.x") }}
known breakage in minor versions	{{ pin_subpackage("myrecipe", max_pin="x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)
known breakage in patch versions	{{ pin_subpackage("myrecipe", max_pin="x.x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)
calendar versioning	{{ pin_subpackage("myrecipe", max_pin=None) }}

while replacing "myrecipe" with either name if a name|lower variable is defined in your recipe or with the lowercase name of the package in quotes.

Bot commands for PR management

Please use the following BiocondaBot commands:

Everyone has access to the following BiocondaBot commands, which can be given in a comment:

@BiocondaBot please update	Merge the master branch into a PR.
@BiocondaBot please add label	Add the please review & merge label.
@BiocondaBot please fetch artifacts	Post links to CI-built packages/containers. You can use this to test packages locally.

Note that the @BiocondaBot please merge command is now depreciated. Please just squash and merge instead.

Also, the bot watches for comments from non-members that include @bioconda/<team> and will automatically re-post them to notify the addressed <team>.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces several updates to the meta.yaml file for the funannotate package. The source package URL format has been modified to a new structure, transitioning from https://pypi.io/packages/source/f/funannotate/funannotate-{{ version }}.tar.gz to https://pypi.org/packages/source/{{ name[0] }}/{{ name }}/funannotate-{{ version }}.tar.gz. Additionally, the build number has been increased from 0 to 1. In the requirements section, a new dependency named distro has been added, and the version constraint for trinity has been changed from a specific version to a range (trinity >=2.15.2). Minor textual adjustments have also been made, including the addition of a period in the summary and the removal of a trailing slash in the documentation URL. These changes collectively enhance the metadata and dependency management for the funannotate package.

Possibly related PRs

• Update meta.yaml for spec2vec #49857: Updates to the meta.yaml file for the spec2vec package include a build number increment and requirements modifications.
• Update panacus recipe to add cmake and c++ dependency #50982: The panacus recipe updates feature changes to build requirements and an incremented build number.
• Rebuild breseq #51221: The breseq package's meta.yaml reflects a build number increment and adjustments to the requirements.
• add meta #51349: Introduction of a new meta.yaml for the meta package with defined dependencies and build requirements.
• Update meta_eukaryome_detect: Rename meta.yml to meta.yaml #51366: Updates to the meta_eukaryome_detect package involve a version increment and dependency changes.
• [biobb_analysis] update 5.0.0 #51431: The biobb_analysis package's meta.yaml updates include a version change and adjustments to dependencies.
• [biobb_cp2k] update 5.0.0 #51528: The biobb_cp2k updates involve version increments and dependency adjustments.
• [biobb_amber] update 5.0.2 #51649: The biobb_amber updates include a version increment and changes to Python version constraints.
• update the biopython dependency for haystac  #51666: The haystac package's version update includes a SHA256 checksum change.
• Update staden_io_lib recipe #51704: The staden_io_lib updates feature a build number increment and new build requirements.
• Rebuild libgff recipe #51746: The libgff recipe updates include a build number increment and changes to host requirements.
• Rebuild ucsc-bedgraphtobigwig recipe #51750: Updates to ucsc-bedgraphtobigwig involve a build number increment.
• Update meta.yaml #51802: The resistify updates include a build number increment and changes to the about section.
• Update meta-neuro version 1.0.0 #51826: The meta-neuro updates involve significant changes to dependencies and the package name.

Suggested labels

please review & merge

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 7b8ba75 and 4950bf3.

📒 Files selected for processing (1)

• recipes/funannotate/meta.yaml (4 hunks)

🔇 Additional comments (5)

recipes/funannotate/meta.yaml (5)

9-9: LGTM! URL update follows best practices.

The URL change from pypi.io to pypi.org and the use of Jinja2 variables ({{ name[0] }}/{{ name }}) follows the standard pattern used in Conda recipes.

---

13-13: LGTM! Build number increment is appropriate.

The build number increment is correct as we're making changes to the recipe (adding new dependency and updating version constraints) without changing the package version.

---

62-62: Verify the trinity version constraint change.

The change from a fixed version to >=2.15.2 makes the dependency less restrictive. Please confirm:

1. Has this been tested with newer versions of trinity?
2. Are there any known compatibility issues with newer trinity versions?

Consider adding an upper bound to prevent potential future incompatibilities (e.g., >=2.15.2,<3.0).

---

96-97: LGTM! Minor text improvements.

The cosmetic changes (adding period to summary and removing trailing slash from doc_url) are acceptable improvements.

---

27-27: Verify the 'distro' package requirement.

Please confirm:

1. Is this dependency required by funannotate?
2. Should we specify version constraints for this package?

---

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.