Renovate: Automate operand version bumps in GPU Operator #1510
Conversation
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
shivakunv
changed the title
shivakunv
requested review from
ArangoGutierrez,
cdesiniotis,
elezar,
shivamerla and
tariq1890
as code owners
shivakunv
commented
Jul 9, 2025
tariq1890
reviewed
Jul 29, 2025
Signed-off-by: Shiva Kumar (SW-CLOUD) <[email protected]>
|
@tariq1890 |
tariq1890
approved these changes
Aug 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Pipeline:
https://github.com/shivakunv/gpu-operator/actions/runs/16165499570
Test PR ( forked repo)
shivakunv#260
driver update skipped
nvcr.io/nvidia/driver
Driver updates were skipped because the driver digest could not be identified.
We are not uploading the images with specefic tags like driver:550 , driver:570 , etc . As a result , Renovate updates all digests with the latest one , which is incorrect .
Possible solution is to adopt SHA256 digest-based updates along with proper tagging.