Update bte to 0.9.1

[BiocondaBot]

Update bte: 0.9.0 → 0.9.1

Info	Link or Description
Recipe	recipes/bte (click to view/edit other files)
Summary	Cython wrapper enabling use of the MAT library in Python.
Home	https://github.com/jmcbroome/BTE
Releases
Author	@jmcbroome

---

This pull request was automatically generated (see docs).

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces several changes to the meta.yaml file for the bte package. The version has been updated from 0.9.0 to 0.9.1, and a new SHA256 checksum has been provided. Additionally, the build number has been reset from 3 to 0, and the skip directive has been removed. A new section titled run_exports has been added, which includes a pinning directive for one of the subpackages.

In the requirements section, the dependency on cython has been modified to specify a stricter version constraint of <1, replacing the previous lack of constraints. Other dependencies listed under both host and run remain unchanged, preserving their specified versions. Overall, the changes reflect updates primarily related to versioning, build configuration adjustments, and a refinement of the cython dependency.

Possibly related PRs

• Update metabolabpy to 0.9.50 #50998: Updates the metabolabpy package's version and SHA256 checksum, similar to the changes made in the bte package.
• Update metabolabpy to 0.9.53 #51094: Also updates the metabolabpy package's version and SHA256 checksum, reflecting similar modifications as in the main PR.
• Update metabolabpy to 0.9.59 #51572: Updates the metabolabpy package's version and adds setuptools to the host requirements, aligning with the versioning updates in the main PR.
• Update metabolabpy to 0.9.63 #51919: Updates the metabolabpy package's version and SHA256 checksum, consistent with the versioning changes in the main PR.

---

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/bte/meta.yaml (1)

17-17: Remove trailing whitespace

There is trailing whitespace on this line.

-  
+

🧰 Tools

🪛 yamllint

[error] 17-17: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between c72c575 and 11a8636.

📒 Files selected for processing (1)

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

🧰 Additional context used

🪛 yamllint

recipes/bte/meta.yaml

[error] 17-17: trailing spaces

(trailing-spaces)

🔇 Additional comments (3)

recipes/bte/meta.yaml (3)

14-14: LGTM: Build number reset

Resetting the build number to 0 is correct for a version update.

---

24-24: LGTM: Cython version constraint

Adding the <1 constraint for Cython is a good practice to prevent potential compatibility issues with future major versions.

---

2-3: Verify SHA256 checksum against upstream release

The version update matches the PR objective. Let's verify the checksum against the upstream release.