Release checks
Operations · Release checks
Operational objective — Turn a source change into a release only after code, artifacts, compatibility, and provenance agree.A release gate that protects users from broken types, missing files, and unsupported runtime behavior.
Key concepts
Source
Tests green
Artifact
Files present
Consumer
Import works
Operational surface
Evidence over assumption
Operational context
Publishing is the last step of a chain; it should not be the first place a package is tested as a consumer would use it.Operator’s principle A release is ready when a clean consumer can use the artifact, not when the repository can build itself.
Implementation notes
Decision lens
Related topics
- scale-balanced · Review support matrix — Read the focused guide for this boundary.
- terminal · Automate checks — Read the focused guide for this boundary.
- cloud-arrow-up · Deploy the artifact — Read the focused guide for this boundary.