[biobb_haddock] update 5.0.0

[PauAndrio]

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 involves an update to the meta.yaml file for the biobb_haddock package. The version of the package has been incremented from 4.2.1 to 5.0.0, necessitating an update to the SHA256 checksum for the source tarball to reflect this new version. Additionally, the dependency on the biobb_common package has been updated from ==4.2.0 to ==5.0.0 in both the host and run requirements, indicating a shift to a newer version of this dependency. The changes are limited to versioning and dependency updates, with no modifications made to the build script, test imports, or other metadata associated with the package.

Possibly related PRs

• [biobb_common] update 5.0.0 #51335: The biobb_common package was updated to version 5.0.0, which is a direct dependency of biobb_haddock, reflecting the same version change.
• [biobb_analysis] update 5.0.0 #51431: The biobb_analysis package also updated its dependency on biobb_common to 5.0.0, aligning with the changes in biobb_haddock.
• [biobb_chemistry] update 5.0.0 #51435: The biobb_chemistry package updated its dependency on biobb_common to 5.0.0, consistent with the updates in biobb_haddock.
• [biobb_cmip] update 5.0.0 #51453: The biobb_cmip package updated its dependency on biobb_common to 5.0.0, maintaining compatibility with the changes in biobb_haddock.
• [biobb_flexdyn] update 5.0.0 #51605: The biobb_flexdyn package updated its dependency on biobb_common to 5.0.0, reflecting the same version change as in biobb_haddock.
• [biobb_godmd] update 5.0.0 #52194: The biobb_godmd package updated its dependency on biobb_common to 5.0.0, aligning with the versioning changes in biobb_haddock.
• [biobb_gromacs] update 5.0.0 #52222: The biobb_gromacs package updated its dependency on biobb_common to 5.0.0, consistent with the updates in biobb_haddock.

Suggested reviewers

• adamhospital
• gbayarri

Warning

Rate limit exceeded

@PauAndrio has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 10 minutes and 6 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between c367fcd and c52fe6a.

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

recipes/biobb_haddock/meta.yaml (1)

23-23: Consider more flexible version constraints for biobb_common

The exact version pinning (==5.0.0) for biobb_common might be too restrictive for future compatibility. Consider using a more flexible version constraint (e.g., >=5.0.0,<6.0.0) to allow for minor updates and patches while preventing breaking changes.

Also applies to: 26-26

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between c367fcd and c52fe6a.

📒 Files selected for processing (1)

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

🔇 Additional comments (2)

recipes/biobb_haddock/meta.yaml (2)

2-2: Verify breaking changes for major version bump

The update from 4.2.1 to 5.0.0 represents a major version change. Please ensure that:

1. Breaking changes are properly documented
2. Migration guide is available for users

Also applies to: 10-10

---

Line range hint 12-18: Build configuration looks good!

The build configuration follows best practices:

• Proper use of noarch: python
• Correct run_exports configuration for ABI compatibility
• Build number reset for new version

🧰 Tools

🪛 yamllint

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

(syntax)