Skip to content

Docker and Crate Publish

Docker and crate publication are separate delivery paths with different credentials, evidence, and review concerns.

Publish Model

flowchart TD
    Candidate[Release candidate] --> Gates[Verify release gates]
    Gates --> Crate[Publish crate]
    Gates --> Image[Build and publish image]
    Crate --> VerifyCrate[Verify crate availability]
    Image --> VerifyImage[Verify image identity]
    VerifyCrate --> Record[Record publish evidence]
    VerifyImage --> Record
    Record --> Announce[Release can be announced]

This diagram is here because crate and image publication are related but not identical. They share release gates, but they diverge in credentials, artifacts, and the evidence a maintainer needs to confirm after publication.

Workflow Anchors

Main Takeaway

Docker and crate publish should never be treated as one vague "release push." Atlas keeps them as separate delivery paths so maintainers can verify crate availability, image identity, provenance, and publish evidence with the right tooling and policy for each artifact class.