Currently we have renovate-image and renovate-version and they are combined with a : in https://github.com/renovatebot/github-action/blob/main/src/docker.ts
I think this makes it impossible to pin to an image digest.
My end-goal is to have Renovate manage the versioning and use pinDigests to ensure we are running a version of Renovate that:
- Meets
minimumReleaseAge
- Is pinned to a digest to remove the risk that a version tag is re-published with a malicious image, after the
minimumReleaseAge
One idea might be to make renovate-image accept a fully specified image+tag. The logic for this might simply look for the presence of a : which would cater for both image:tag and image@SHA256:digest.
Currently we have
renovate-imageandrenovate-versionand they are combined with a:in https://github.com/renovatebot/github-action/blob/main/src/docker.tsI think this makes it impossible to pin to an image digest.
My end-goal is to have Renovate manage the versioning and use
pinDigeststo ensure we are running a version of Renovate that:minimumReleaseAgeminimumReleaseAgeOne idea might be to make
renovate-imageaccept a fully specified image+tag. The logic for this might simply look for the presence of a:which would cater for bothimage:tagandimage@SHA256:digest.