ublue-os/main build failures (Renovate)
I'm not sure what's going on but I gotta crash, hoping @Robert will have some insight when I wake up 
RI've spent some time looking into this... And I'm a bit confused...
My best guess would be images were pushed, then deleted.
It seems like Timothee ran the pipelines twice a few hours ago, and since the image tags are YYYYMMDD, the old image (which Renovate pinned us to) is no longer tagged, and was potentially garbage collected due to having no tags.
My best guess would be images were pushed, then deleted.
It seems like Timothee ran the pipelines twice a few hours ago, and since the image tags are YYYYMMDD, the old image (which Renovate pinned us to) is no longer tagged, and was potentially garbage collected due to having no tags.
RI've triggered Renovate to run again, so it should find the updated digests and update the existing PR.
Renovate runs every 4 hours it seems, so should have been picked up after not too long anyway.
Renovate runs every 4 hours it seems, so should have been picked up after not too long anyway.
BThank you for looking!
Your understanding and explanation are better than mine. I’d wondered if something unexpected happened upstream but didn’t go look yet.
Your understanding and explanation are better than mine. I’d wondered if something unexpected happened upstream but didn’t go look yet.
RIt happened again - two images were pushed to the same tag within the same hour, Renovate pinned us to the first image but it was garbage collected. Not quite sure the best way to resolve this...
RSo I've grouped all image updates together in ublue-os/main, so a single PR bumps base images and akmods. This prevents the blockage when there's a kernel update.
Also configured Renovate to automatically rebase the PRs when the base branch is updated.
Let's see if this fixes the issues...
Also configured Renovate to automatically rebase the PRs when the base branch is updated.
Let's see if this fixes the issues...
