chore: pin dev dockerfile go base image and distroless base image #726
Conversation
WalkthroughThe Docker builder image now uses ChangesContainer image pinning
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
There was a problem hiding this comment.
Pull request overview
Pins container base images by switching to digest-qualified (@sha256:...) references for the release and dev Docker build flows, improving supply-chain reproducibility.
Changes:
- Pinned the distroless runtime image in
.goreleaser.Dockerfileto an exact digest. - Pinned the Chainguard Go builder image in
.dev.Dockerfileto an exact digest (but changed the tag tolatest).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| .goreleaser.Dockerfile | Pins the distroless runtime base image via digest for reproducible release images. |
| .dev.Dockerfile | Pins the dev builder base image via digest (currently uses a latest tag with the digest). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
🧹 Nitpick comments (1)
.dev.Dockerfile (1)
1-1: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winRetain the intended Go version alongside the digest.
This changes the declared base from
go:1.25togo:latest. Prefergo:1.25@sha256:...and verify that the digest resolves to the intended Go 1.25 image; otherwise this pin can silently select a different toolchain lineage during future maintenance.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.dev.Dockerfile at line 1, Update the builder image declaration to use the explicit go:1.25 tag together with the existing digest, rather than go:latest. Verify that the digest corresponds to the intended Go 1.25 image before retaining it.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In @.dev.Dockerfile:
- Line 1: Update the builder image declaration to use the explicit go:1.25 tag
together with the existing digest, rather than go:latest. Verify that the digest
corresponds to the intended Go 1.25 image before retaining it.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: f25c83d8-131c-49c4-8366-19b5eec607b4
📒 Files selected for processing (2)
.dev.Dockerfile.goreleaser.Dockerfile
Description
What problem is being solved?
How is it being solved?
What changes are made to solve it?
References
Review Checklist
mainSummary by CodeRabbit