fix(renovate): disable digest pinning for devfile base-developer-image#807
Conversation
The image only publishes rolling tags (ubi10-latest) with no semver releases, so pinning the digest creates churn without supply-chain benefit -- the tag itself is already a derived latest. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
🚧 Files skipped from review as they are similar to previous changes (3)
📝 WalkthroughWalkthroughRemoves SHA256 digest pins from the ChangesUnpin devfile base-developer-image
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Co-authored-by: Miguel Angel Ajo Pelayo <majopela@redhat.com>
Summary
quay.io/devfile/base-developer-imagesince the image only publishes rolling tags (ubi10-latest) with no semver releases@sha256:...digests frompython/.devfile/ContainerfileandContainerfile.clientpinDigests: falseto the devfile package rule inrenovate.jsoncTest plan
ubi10-latesttag without attempting to pin a digest🤖 Generated with Claude Code