Update cuml-cu13 version in requirements.txt

[ktangsali]

PhysicsNeMo Pull Request

Description

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.
• The CHANGELOG.md is up to date with these changes.
• An issue is linked to this pull request.
• If I am implementing a new model or modifying any existing model, I have followed the Models Implementation Coding Standards.

Dependencies

Review Process

All PRs are reviewed by the PhysicsNeMo team before merging.

Depending on which files are changed, GitHub may automatically assign a maintainer for review.

We are also testing AI-based code review tools (e.g., Greptile), which may add automated comments with a confidence score.
This score reflects the AI’s assessment of merge readiness and is not a qualitative judgment of your work, nor is
it an indication that the PR will be accepted / rejected.

AI-generated feedback should be reviewed critically for usefulness.
You are not required to respond to every AI comment, but they are intended to help both authors and reviewers.
Please react to Greptile comments with 👍 or 👎 to provide feedback on their accuracy.

[greptile-apps]

Greptile Summary

This PR bumps cuml-cu13 in the DoMINO example's requirements from the wildcard pin 25.10.* to the exact pin 26.2.0, and fixes a missing trailing newline. No other dependencies or code are touched.

• Version bump: cuml-cu13==25.10.* → 26.2.0 (RAPIDS October 2025 → February 2026 release); the exact pin improves reproducibility but will no longer receive patch releases automatically.
• Newline fix: Adds a missing newline at end of file.

Important Files Changed

Filename	Overview
examples/cfd/external_aerodynamics/domino/requirements.txt	Updates cuml-cu13 from the wildcard 25.10.* to the exact pin 26.2.0, and adds a trailing newline. No other dependencies are changed.

_{Reviews (1): Last reviewed commit: "Update cuml-cu13 version in requirements..." | Re-trigger Greptile}

[ktangsali]

Re-opening a clean version of this: #1657

[peterdsharpe]

LGTM

Probably nothing, but what's the diff at the EOF here? Carriage return vs. no? Newline at the bottom?