Skip to content

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

Open
kuzdogan wants to merge 1 commit into
stagingfrom
renovate-no-pin-own-images
Open

chore(renovate): never digest-pin our own ghcr images#2944
kuzdogan wants to merge 1 commit into
stagingfrom
renovate-no-pin-own-images

Conversation

@kuzdogan

Copy link
Copy Markdown
Member

Summary

Renovate opened #2925 (pin ghcr.io/argotorg/sourcify/server docker tag to a digest) because pinDigests: true adds a digest to every image that has none. That is a false positive: services/server/docker-compose.yml points self-hosters at server:latest on purpose, and a pinned digest would freeze them on one build.

The existing rule that disables digest updates does not cover this case, because the first pin is a separate update type (pinDigest). This adds a package rule that sets pinDigests: false for ghcr.io/argotorg/sourcify/**. Third-party images (postgres, node) stay pinned as before.

Closes the Renovate PR #2925 (server digest pin).

🤖 Generated with Claude Code

docker-compose.yml points self-hosters at server:latest on purpose. The
pinDigests rule tried to freeze it to one build (#2925).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@kuzdogan kuzdogan moved this from Triage to Sprint - Needs Review in Sourcify Public Aug 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Sprint - Needs Review

Development

Successfully merging this pull request may close these issues.

2 participants