Browse documentation

Release distribution

Publish immutable versions or select temporary rolling Runs deliberately.

Releases turn verified build evidence into an intentional distribution contract. A product is a permanent project-scoped distribution identity. An immutable version identifies a successful exact Job Run, its source commit, artifacts and recorded digests. Publishing does not automatically put that version on a channel or deploy an App.

Versions and channels

Publishing an unattached version leaves it project-only. A Release channel belongs to one product, has project-only or public access, a set of version members, and an optional current tip. Membership and tip are separate: a previous public member may remain available at its exact version URL when a newer version becomes the tip. Attaching and promoting to an existing channel is an explicit, guarded decision. An empty public channel exposes no version bytes.

A product may designate a default channel for discovery. If that default is unavailable or ineligible for the viewer, clients must not silently choose another channel or assume one named stable. Canonical generated API URLs use the immutable project key and channel's durable numeric identity rather than the editable project display name or channel name. Projects and access explains why those identities are not permissions; the API introduction identifies the programmatic route boundary.

Public access is narrow: it allows anonymously addressed distribution records and files for eligible public channel members. It does not expose project discovery, Jobs, Run provenance, product administration, or browser Releases pages without authorization. Project-only and unattached versions need the appropriate API token or signed-in browser access. Even a previously discovered URL is checked for access and file integrity when used.

Rolling is deliberately temporary

A rolling channel instead binds to a same-project Job and lists currently stored, eligible successful Runs. It has no immutable Release members or tip and creates no Run retention hold. Its visible current build may change or disappear as Runs complete, become ineligible or are removed. Consumers must pin the selected channel, Job, Run, source SHA, and artifact evidence rather than mistaking a rolling view for an immutable version. There is no automatic fallback from a missing Run to a Release.

Lifecycle is not an update announcement

Deprecation warns that a version should no longer be used while retaining authorized bytes; publishing a newer version alone is not deprecation. Revocation stops new exact downloads while preserving the version's audit and build evidence. Withdrawing a version from a public channel removes its public access unless another authorized path remains. These changes are consequential management actions, not a way to display routine update notices.

For the action and its checks, publish a Release; for public read-only discovery, see the Release channel API. See Jobs and Runs for the evidence that publication starts from.