fix: pin all external refs to cryptographic identity (closes #118) #119
No reviewers
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
merge-ready
merge-ready
needs-checks
needs-checks
needs-rebase
needs-rebase
needs-review
needs-review
needs-rework
needs-rework
notplanned
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sneak/upaas#119
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "fix/pin-external-refs-crypto-identity"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Changes
golang:1.25-alpineandalpine:3.19base images to sha256 digestsgolangci-linttov2.10.1andgoimportstov0.42.0(was@latest)make checkoutputAll checks passed with zero failures.
Closes #118
Pipeline sweep: PR is mergeable and CI checks passed. No code review yet — labeling
needs-review. Spawning review agent.Code Review: PR #119
Summary
Clean, focused PR that pins Docker base images to SHA256 digests and Go tool installs to specific versions in the Dockerfile. Only 1 file changed, 4 lines modified.
Checks
Changes Reviewed
Minor Observation (non-blocking)
The Go tool installs in the Dockerfile use semver tags (@v2.10.1, @v0.42.0) while the CI workflow uses commit SHAs. Both are acceptable since Go module proxy serves immutable checksum-verified content for version tags. Using commit SHAs in the Dockerfile too would be maximally consistent but is cosmetic.
Verdict: LGTM
PR achieves its stated goal cleanly. All external Docker image references use cryptographic digests. Go tool versions are pinned. No config weakening. Ready to merge.
e367c2dd5bto0ed2d02dfeUpdated: replaced version tags (
@v2.10.1,@v0.42.0) with commit SHAs to match CI workflow and ensure true cryptographic pinning.make check: ✅ All checks passed!Reviewed the diff — all Docker
FROMstatements andgo installcommands in the repo now use cryptographic identity (sha256 digests / commit SHAs). The CI workflow was already correctly pinned.