Skip to content
PREFLIGHT 0.9.0
Menu

Updating image pins#

This page covers the image pins Preflight's components run: why they are digests, how to look one up, and how to change one. Read the pinning rules, look up the new digest, and open a reviewed merge request. Like the aircraft preflight it is named after, the value shows up on the day it catches something.

Why pins are digests#

Every image the components run is pinned by digest (name:tag@sha256:...), so a repointed tag cannot quietly change what a pipeline executes. The tag stays in front of the digest so a diff still reads like a version bump.

Look up the digest#

To look up the digest for an image:

docker buildx imagetools inspect <image>:<tag>

Use the top-level Digest: line (the multi-arch index digest), not a per-platform one. Without buildx, docker manifest inspect -v <image>:<tag> shows the same index digest.

Change a pin#

Pins change only through a reviewed merge request.

  • Dependency caching: the image_prefix input in front of each pin, and the package caches.
  • Template lint: the unsafe CI patterns composer ci scans for before the fixture tests.
  • Shared conventions: Composer vendor, license, PHP floor and JavaScript installs.