## **User description** ### **User description** Update dependency ### **PR Type** Enhancement, Other ### **Description** - Update `cantera` dependency to flexible version constraint (>=3.1.0) - Switch `pyrometheus` repository to official bryngelson fork - Remove Python 3.13 setup from CI test workflow ### Diagram Walkthrough ```mermaid flowchart LR A["Dependencies"] -->|cantera: pinned to flexible| B["cantera>=3.1.0"] A -->|pyrometheus: fork update| C["sbryngelson/pyrometheus-bryngelson"] D["CI Workflow"] -->|remove setup| E["Python 3.13 step removed"] ```

File Walkthrough

Relevant files

Dependencies

pyproject.toml

Update chemistry dependencies and repository sources

toolchain/pyproject.toml

Update cantera from pinned version 3.1.0 to flexible constraint
>=3.1.0
Change pyrometheus repository from wilfonba/pyrometheus-wilfong to
sbryngelson/pyrometheus-bryngelson
Both dependencies maintain the OpenMPTest branch reference

+2/-2

Configuration changes

test.yml

Remove Python 3.13 from test workflow

.github/workflows/test.yml

Remove Python 3.13 setup step from CI matrix configuration
Eliminates the actions/setup-python@v5 action for Python 3.13

+0/-5

___ ## **CodeAnt-AI Description** Update chemistry dependencies and CI to match modern Python tooling ### What Changed - Cantera now allows any 3.1+ release and pyrometheus installs from the official repo so chemistry tooling uses the maintained sources. - The GitHub Actions test job runs with Python 3.14 in place of the removed 3.13 setup. ### Impact `✅ Chemistry stack tracks maintained releases` `✅ pyrometheus installs from official repository builds` `✅ Tests cover Python 3.14 runtime`

💡 Usage Guide

### Checking Your Pull Request Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later. ### Talking to CodeAnt AI Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code. #### Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

### Preserve Org Learnings with CodeAnt You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards. #### Example

@codeant-ai: Do not flag unused imports.

### Retrigger review Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

### Check Your Repository Health To analyze the health of your code repository, visit our dashboard at [https://app.codeant.ai](https://app.codeant.ai). This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

## Summary by CodeRabbit * **Chores** * CI updated to use Python 3.14 (replacing 3.13). * Minimum supported Python raised (effective minimum bumped to 3.11; some toolchain profiles now use 3.12). * Relaxed cantera requirement to allow versions >=3.1.0. * Switched pyrometheus dependency to the upstream repository. * Toolchain profiles cleaned and standardized: removed legacy/duplicate entries and added updated platform blocks. _{✏️ Tip: You can customize this high-level summary in your review settings.}