Three reference forms
| Form | Example | Behavior |
|---|---|---|
| Local alias | benchmark | A convenient name in your local Fleet Store. You can repoint it. |
| Registry tag | team/repo:v1 | A repository handle for a root. Mutability follows Repository policy; new Repositories make only latest mutable by default, and policy or freezing can make it immutable. |
| Root digest | sha256:… | The exact immutable content identity. Equal digests mean equal canonical bytes. |
Recommended release practice
- Publish changed content under a new release tag such as
v2. - Pin digests in automation that must reproduce exact bytes.
- Use
--no-latest-retagwhen a push must not movelatest. - Compare digests—not tag text—when checking whether two references are identical.
A TaskSet is a complete closure
Publishing a TaskSet transfers its immutable root plus every Environment and Artifact it references. Runtime receives complete Task inputs and authoritative digests. It never resolves a Registry name during execution or patches Task content.
Read and compare version history
A Repository retains immutable roots even when its tag bindings move. Several tags can resolve to the same root, while any identity-bearing edit produces a new digest. Use an exact reference such as acme/evals@sha256:… when a workflow must not follow a tag. Historical Runs remain pinned to their recorded TaskSet digest. In Registry, open Tasksets → repository → Versions → Compare versions to compare exact Task additions, removals, identity changes, and possible digest-preserving renames. Catalog counts are labeled Tags; they are current bindings, not a count of every immutable root retained in version history.