A release label moves to a new artifact while an existing container and another label still refer to the old one.

Image tags can move while existing containers keep their image

An image tag is a readable name associated with an image reference. Unless a registry policy prevents reassignment, the same tag can later identify another artifact. Tags such as v1.4 and latest differ in naming convention, not in an inherent guarantee of immutability. Reproducing a deployment requires recording the artifact actually selected, together with the platform and runtime configuration that determined its behavior. ...

August 24, 2027 · 5 min · XB Field Notes
Observe, decide, and act panels for promoting a verified artifact.

Promote a verified artifact through environments

A staging test establishes facts about the artifact and environment that actually ran. Building again before production creates another output whose identity must be checked or whose behavior must be revalidated. Promotion carries an already verified artifact to the next environment and records that decision. It removes one source of uncertainty, but it does not make staging and production equivalent or eliminate the need to verify the resulting deployment. ...

February 17, 2027 · 5 min · XB Field Notes
Observe, decide, and act panels for reviewing a version change.

Semantic versioning makes compatibility explicit

A dependency version is useful when its publisher and consumers agree on the public contract. Semantic Versioning gives changes a vocabulary: from version 1.0.0 onward, incompatible public API changes require a major increment, compatible additions require a minor increment, and compatible fixes require a patch increment. The number summarizes a claim about a release. It does not inspect its implementation or guarantee that an upgrade will work in your application. ...

February 13, 2027 · 4 min · XB Field Notes