RIt manages multiple digests in a YAML, Renovate bumps the digest and it can be configured to auto merge
Jright
Joh my god
RSo all base images, and other downstream dependencies in a single file
JRIGHT
Jso in bluefin if silverblue-main gets rebuilt just PR, automerge, and kick off a build.
Jand so on?
RYeah
Jdude
Jcan we do timothee's?
Jlike instead of cron guessing all the time
RI don't see why not
JYES
Jdude we can just get rid of crons
J@M2 AND when you make a change in say akmods, and merge it, the entire rest of the world will rebuild
Jwe don't need to do the dumb "and add an hour of padding" each time
Jok so I can make this in bluefin now say, but adjust it to follow silverblue main?
Jactually LTS following the centos one should do the trick
RThe config which does this is here
https://github.com/rsturla-homelab/renovate-config/blob/main/org-inherited-config.json#L53-L64
So the GitHub Actions workflow would decide which image to use based on the "name" field. It's just a selector.
https://github.com/rsturla-homelab/renovate-config/blob/main/org-inherited-config.json#L53-L64
So the GitHub Actions workflow would decide which image to use based on the "name" field. It's just a selector.
Jok I'm going to draft a PR for LTS so I can figure it out.
RTo start with, you don't even need to hook it up. Just commit the image-versions.yml file to the repo, add the Renovate config and make sure it bumps the versions as you'd expect
Jon it now.
JGitHub
To track the upstream releases of centos.
Jcan we add this renovate config org wide so all we have to do is add these to each repo?
RWe can do it org-wide. I didn't think it was possible until a few weeks ago
Joh man this is AWESOME
Jshow me where I can do it
RWe need to make a renovate-config repo (name is important)
RAnd add the global config file named "org-inherited-config.json" to the root of the repo
RAnd done
Jok I can do that,
renovate-config?JRCool! Should I push a config that should work?
Jhell yeah!
Jgo for it!
Jwhatever you think is best for renovate to do IMO
RTo start with, it won't be anything too controversial. Just best-practices preset and managing that YAML file
Jright!
Jyeah set this one file to automerge, and then for the others we can just discuss as they come up
JMAN THIS IS AWESOME
RLet's merge your bluefin PR next, and we should see version bumps
Jcopilot fixed my typo. 
Jjust merging since we didn't touch the image
ROnce this works, we would just need to add logic to the workflow to extract the registry, tag and digest from the YAML, and use it in the Containerfile's FROM line
Or I think there's a CLI argument in
Or I think there's a CLI argument in
podman build to build from a specific base imageJThis is soooooo good.
RSomething didn't work... Checking
R
RGitHub
This PR contains the following updates:
Package
Update
Change
quay.io/centos-bootc/centos-bootc
digest
feea845 -> 35be01f
Configuration
Schedule: Branch creation - At any time (...
Package
Update
Change
quay.io/centos-bootc/centos-bootc
digest
feea845 -> 35be01f
Configuration
Schedule: Branch creation - At any time (...JYEAH!!!!
