Releases & rollback

A release is the unit of deployment: a build, a resolved config, and a stage, rendered to a manifest and reconciled.

What a release is

When you deploy, High resolves build × config × stage into an internal manifest (the IR) and hands it to the engine, which reconciles your outposts toward it. The release gets an id like r-204 and moves through the deployment phases as it converges.

Preview before you deploy

You can render a release without applying it — a preview resolves the exact manifest and runs the same validation a deploy does, so conflicts and capability gaps surface as plain warnings instead of a broken rollout. A raw outpost that can't autoscale, two routes fighting over a port, a missing secret: caught here, before anything changes.

Rolling back

Every release is retained, so a rollback is simply re-applying a prior one — there is no separate undo mechanism. Re-apply r-203 and the engine reconciles back to that exact manifest.