Add automated upgrade workflow for halide-llvm#8948
Merged
alexreinking merged 3 commits intomainfrom Feb 17, 2026
Merged
Conversation
alexreinking
added
skip_buildbots
Member
Author
|
There is no way to test this workflow until it is merged. Can I get a rubber-stamp here, please? |
shoaibkamil
approved these changes
Feb 17, 2026
Contributor
shoaibkamil
left a comment
shoaibkamil
left a comment
There was a problem hiding this comment.
It sounds like we're unable to test the new workflow fully before merge, but this won't break buildbots etc as the pyproject.toml changes have been tested in the PR.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rather than dependabot (#8947) we can use a custom GHA workflow to schedule updates for our
halide-llvmversion.Pinning a particular version in the
pyproject.tomlis the wrong idea -- theuv.lockmanages the consistent set, while thepyproject.tomlmanages the constraints. Under this interpretation, the constraint is that LLVM 22 should be... a version of LLVM 22. But it'suv.lockthat says we're on 22.1.0rc3 (for example). Similarlyci-llvm-mainsays we depend on even a pre-release version of LLVM 23 (via the.dev0constraint).For reference, one can regenerate
uv.lockafter a change topyproject.tomlby runninguv lock. One can upgrade a particular package viauv lock -P halide-llvm(for example) followed byuv sync [--group ci-llvm-NN].