Allow packages from the distribution's own package index unpinned (closes #72)
check / check (push) Canceled after 0s
check / check (push) Canceled after 0s
A package from the distribution's own package index now needs no version and no hash, and pulling that index is allowed, on sneak's answer at #72 (comment). The distribution is the pinned base image's in a Dockerfile and the host's on a host. It is trusted, and everything else stays pinned by hash. A package source that a Dockerfile adds itself does not get the exception. The pinning rule of REPO_POLICIES.md and both checklists say so, and the canonical Go Dockerfile's apk add line has a comment saying why it is allowed. Model: opus-5-5
This commit was merged in pull request #145.
This commit is contained in:
1 parent
229ea67434
commit
b656617183
4 files changed
+56
-20
No files matched your search
@@ -243,7 +243,11 @@ are thin shims calling them. Model scripts:
|
||||
final stage is missing its `COPY --from=` edge to the gate phases.
|
||||
- [ ] No secrets in repo, and none in the build context: enumerate a probe image
|
||||
rather than reading `.dockerignore`
|
||||
- [ ] No mutable image/package references
|
||||
- [ ] No mutable image/package references. The one exception is a package from
|
||||
the distribution's own package index, which needs no version and no hash.
|
||||
Pulling that index is also allowed. In a `Dockerfile`, the distribution is
|
||||
the pinned base image's. On a host, it is the host's. A package source
|
||||
that a `Dockerfile` adds itself does not get this exception
|
||||
- [ ] No unnecessary files in repo root
|
||||
- [ ] All dates written as YYYY-MM-DD
|
||||
|
||||
|
||||
Reference in new issue
Block a user