Application Versioning Overview

Application versioning lets Creators manage changes to an Unqork application using branches and published versions. Creators work on a branch, publish it as a named version when ready, and promote that version across environments independently.

To begin using application versioning, read the sections below.

Important: Enabling versioning is permanent. Once enabled on an application, it cannot be turned off.

Key Concepts

Understanding these terms helps Creators use Unqork's application versioning effectively.

• Branch: A working copy of the application where Creators make changes. Branches are editable. Multiple branches can exist at the same time.
• Version: A published snapshot of a branch at a point in time. Versions are read-only. To make changes, create a branch from a version first.
• Default version: The version that displays when no version context is in the URL. Other applications reference the default version when they set the application as a dependency.
• Promoting: Moving a published version across environments (Staging, UAT, Production) independently of other versions.

When to Use Application Versioning

Application versioning is well suited for teams that need to:

• Protect the live application while developing new features or fixes on a separate branch.
• Support parallel workstreams so multiple teams can develop on separate branches without blocking each other.
• Promote a specific version to Staging, UAT, or Production without including unfinished work from other branches.
• Roll back quickly by setting an earlier published version as the default if a promoted version causes issues.
• Let other applications pin to a stable, named version of yours as a dependency.

Enable Application Versioning

Enabling versioning is a one-time setup step. Before beginning, note the following:

Important: Enabling versioning creates v0.0.0 as the first version of the application. The platform automatically detects and adds external dependencies. Versioned applications do not support library modules. Move shared modules to a separate application and set it as a dependency first.

Creators can enable versioning when creating a new application or on an existing one.

New Application

To enable versioning while creating an application:

1. In the Explorer, click + Create Application.
2. Complete the application details.
3. Turn on Enable Application Versioning.
4. Click Create.
5. Review the Enable versioning? dialog and click Enable versioning to confirm.

Existing Application

To enable versioning on an application that already exists:

1. In the Explorer panel, click the (ellipsis) next to the application.
2. Select Settings from the drop-down.
3. In the settings dialog, find the Versioning section and click Enable versioning.
4. Review the Enable versioning? dialog and click Enable versioning to confirm.

After enabling, v0.0.0 becomes the active default version. All future edits happen on branches. The checkout pill displays in the module toolbar so Creators always know which branch or version is active.