Browse documentation

Release distribution URLs

Use exact immutable version URLs and durable channel selection.

Repopack distinguishes build evidence (a Job Run), immutable publication (a Release version) and selection (a channel). A plain publication does not attach the version to a channel, and a channel named stable is never inferred. See Release concepts and publish a Release before automating delivery.

In the project workspace, press r to open that project's Releases page if you have Releases read access. It opens the page directly, not a search palette. The shortcut leaves the key alone while you're typing, using the chat workspace, or interacting with a dialog.

Exact Release addresses

Programmatic records and downloads use the permanent project key, product name and exact version:

/api/v0/projects/<key>/releases/products/<product>/versions/<version>
/api/v0/projects/<key>/releases/products/<product>/versions/<version>/artifacts/<name>
/api/v0/projects/<key>/releases/products/<product>/versions/<version>/attachments/<name>

A version in a public channel can be accessed anonymously through its exact URL; private or unattached versions require a valid bearer token with release.read. An invalid or expired token fails instead of falling back to anonymous access. Browser /project/<key>/releases/… pages use session authentication and are not API URLs. Private responses are no-store. Public exact responses can use strong evidence ETags with revalidation, but access, lifecycle and bytes are checked again before a conditional response. Verify downloaded bytes against the recorded SHA-256 and size; missing or changed bytes fail rather than silently serving corrupt artifacts. Deprecation retains authorized access with an HTTP Warning: 299 header; revocation cuts off exact records and bytes with 410 while keeping audit history.

Channels and durable selection

Create a channel explicitly with rp release channel create <product> <channel> --visibility project|public. It starts empty. A channel has membership and an optional tip; withdrawing a non-tip member differs from clearing a tip. Channel creation and sensitive changes require guarded confirmation. rp release channel list, show and members reveal the viewer-authorized channels; a canonical channel URL uses the numeric id-<channel-id>, which survives display-name changes. Discover eligible channels with the version-2 channel API; default_channel: null means do not select a fallback.

A rolling channel instead binds to a same-project Job and lists currently eligible successful Runs. It is mutable and does not create immutable versions or Run retention holds. Consumers should pin the returned channel identity, Job, Run, full source SHA and artifact digest; an absent or ineligible Run must not silently switch to another build. Run retention explains why rolling is unsuitable as a long-term archive.