Skip to content

chore(renovate): never digest-pin our own ghcr images #2944

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kuzdogan merged 1 commit into from
Aug 31, 2026
Merged

chore(renovate): never digest-pin our own ghcr images #2944

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions renovate.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,11 @@
"description": "No routine digest churn. A new upstream digest is not evidence that ours is bad, and a rebuilt base image is not reviewable — a weekly stream of opaque hash bumps trains people to rubber-stamp them. We bump a pin deliberately when something tells us the pinned image is actually vulnerable. Note this only stops refreshes of existing pins: pinDigests still adds a digest to any newly introduced image.",
"matchUpdateTypes": ["digest"],
"enabled": false
},
{
"description": "Never digest-pin our own images. docker-compose.yml points self-hosters at server:latest on purpose, so a pinned digest would freeze them on one build.",
"matchPackageNames": ["ghcr.io/argotorg/sourcify/**"],
"pinDigests": false
}
],
"pinDigests": true,
Expand Down