Browse documentation

Publish a Release

Check build evidence and deliberately publish a version to a channel.

Publishing turns a verified successful Job Run into an immutable Release version.

Publication requires an explicit decision

This guide assumes the product and intended channel already exist, you have publication authority, and your project's version-cut checks are complete. It is not permission to publish or promote a version just because a Run succeeded.

Check the source and destination

rp job runs <job-number>
rp release product show <product>
rp release channel show <product> <channel>

Scroll horizontally to read full commands.

Confirm the Run's result, exact source SHA, artifact evidence, version, intended channel and its visibility. A public channel makes eligible exact version downloads public. Do not substitute a rolling channel for an immutable version or assume a channel named stable is your project's default.

Preview, then publish deliberately

For an approved publish-and-go-live action, preview the same proposed publication first:

Preview the publication

rp release publish <product> <version> --job <job-number> --run <run-number> --promote-to <channel> --dry-run

Scroll horizontally to read the full command.

Publish after the checks agree

rp release publish <product> <version> --job <job-number> --run <run-number> --promote-to <channel>

Scroll horizontally to read the full command.

The second command is guarded and publishes, attaches and promotes in one confirmation. --promote-to does not create a channel or change its visibility. If the intention is inspection without making a version available on a channel, omit --promote-to and publish unattached; that version remains project-only. Do not run the second command until the dry-run plan and all independent release checks agree.

Check the resulting version and channel with rp release show <product> <version> and rp release channel show <product> <channel>. Verify downloads and hashes through the authorized distribution path before announcing a release. Release discovery explains the public read boundary; it does not replace publication approval or byte-integrity checks.