Skip to content

Conversation

@njhill
Copy link
Member

@njhill njhill commented Dec 7, 2025

Used claude code for this.

I think an alternative option could be to use .in files like we already do for the test dependencies.

Resolves #28071.

@mergify mergify bot added ci/build nvidia rocm Related to AMD ROCm labels Dec 7, 2025
@njhill njhill mentioned this pull request Dec 7, 2025
1 task
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a robust mechanism for pinning dependency versions using pip constraints, which is a significant step towards ensuring reproducible builds. The implementation across the various Dockerfiles is well-executed, and the addition of the compile_constraints.sh script and the detailed README.md is commendable. I have identified one critical issue in the constraint generation script for ROCm builds that could lead to incorrect dependencies being installed. The fix is straightforward and detailed in the review comment.

Signed-off-by: Nick Hill <[email protected]>

Co-authored-by: Claude Code
Signed-off-by: Nick Hill <[email protected]>
For ROCm Docker builds

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Nick Hill <[email protected]>
./compile_constraints.sh
```

This will resolve all dependencies to their latest compatible versions available on PyPI.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given that we're trying to insulate ourselves from package versions that break us, we are expecting this updated package set to break with some regularity ... and yet we do want to update to the latest version of dependencies as quickly as possible

In #28071 you're suggesting (I guess) running compile_constraints.sh in an updated job that will submit a PR.

When that fails, someone will narrow down which package broke us, and submit a separate PR with a version block in requirements/*.txt e.g. requests!=2.16.1,>= 2.26.0 ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@markmc yes exactly, or adjust code accordingly. But as also discussed in that issue, perhaps dependabot can be used to automate opening the PRs rather than a job that runs the script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci/build nvidia rocm Related to AMD ROCm

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

[RFC]: Pin all dependencies

2 participants