Releases

A release is a snapshot of a branch at a point in time. Once created, its contents never change - you deploy it to an environment, download it, or return to it later if you need to roll back. Releases store content by reference, so creating one is fast and doesn’t duplicate your files, no matter how large your project is.

​

The Releases page

Open Releases from the sidebar. The page has two sections:

• Your environments at the top - the deploy targets for this project and which release each one is serving. If you see “No environments configured yet. Add one from project settings to start deploying.”, set one up first. See Environments.
• All releases below, filtered by Published, Drafts, or All.

Each release shows its version or name, a draft or published badge, who created it and when, its description, and a “live on” chip for every environment currently serving it. The row menu offers Publish…, Update…, and Remove…, and a download button saves the release as a ZIP.

​

Create a release

1. Click Create release.
2. Pick the branch to snapshot.
3. Enter a name and, optionally, a description of what’s in the release.
4. Choose how the version should change: Patch, Minor, or Major. You can also keep the release as a draft and publish it later.
5. Review the Pre-flight block, then click Create release.

As soon as you pick a branch, pre-flight checks run against it: test cases, static analysis, and whether environments are available to deploy to. Green checks mean the branch is in good shape to release. Pre-flight is the same safety net you see when saving changes - see Review & save.

​

Choosing a version increment

Published releases follow semantic versioning (MAJOR.MINOR.PATCH):

​

Drafts and publishing

A draft is a release without a version number. Use drafts to package work in progress, share a snapshot with reviewers, or stage something you plan to publish later. Drafts appear under the Drafts filter and carry a draft badge. To publish a draft, open Publish… from its row menu, pick the version increment, and confirm. The release gets the next semantic version and moves to the Published filter.

​

Deploy a release

Click a release to open the deploy view. Pick an environment to push this release to - the pre-flight checks at the top confirm tests and configuration are good to go. Each environment card shows its current state: the version that’s live, “Idle - no release deployed yet.” if nothing is deployed, or “This release is already live here.” when the environment is already serving this release. Select an environment and click Deploy. Environments marked with a “requires review” chip don’t deploy directly. For those, the button reads Open review to deploy: clicking it opens a deploy request, and the release goes live once the request is approved. See Requests.

​

Download a release

Use the download button on a release row, or Download ZIP in the deploy view, to save the release as a ZIP archive. The archive contains the release’s decision graphs and policies, so you can keep it for audit purposes or evaluate it outside the platform.

​

Update or remove a release

Update… lets you edit a release’s name and description - useful for adding change notes after the fact. The snapshot itself stays untouched. Remove… deletes the release permanently.