renovate: run update_artifacts_lockfile as postUpgradeTasks - #4606
Conversation
When Renovate bumps the openshift-client version in ci/hermetic/artifacts.lock.yaml it only updates the download_url, leaving stale sha256 checksums that break hermetic builds. Configure postUpgradeTasks to run update_artifacts_lockfile after each version bump so the checksums are refreshed in the same PR. Also add command-line argument support to update_artifacts_lockfile so it can be called from the repo root with the lockfile path as an argument rather than requiring the caller to cd into ci/hermetic/ first. Depends on KONFLUX-9132 to add update_artifacts_lockfile to the mintmaker-renovate-image and its allowedCommands list. Assisted-by: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Skipping CI for Draft Pull Request. |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
/do-not-merge as this PR has no effect until the two konflux-ci PR's listed in the description merge. |
When MintMaker bumps the OpenShift client version in ci/hermetic/artifacts.lock.yaml it only updates the download_url fields, leaving the checksum fields pointing at the old version. The hermetic build then fails because the downloaded file doesn't match the stored fingerprint. Example: PR #4524.
postUpgradeTasks is a standard Renovate feature that runs a shell command after a dependency is updated. This PR adds it to the custom.oc package rule so MintMaker calls update_artifacts_lockfile immediately after bumping the OC version, refreshing all four architecture checksums in the same PR commit.
update_artifacts_lockfile is also updated to accept the lockfile path as a command-line argument (sys.argv[1]), since MintMaker runs from the repo root and needs to pass the full path. The original no-argument behavior is preserved as a fallback.
This PR has no effect until the following are merged and deployed:
See: https://issues.redhat.com/browse/COS-3382