Loading Leap…

Versions and Deployments

Create versions of your merged design, manage environments, and deploy a version to an environment.

Versions and Deployments

Once your design works, it's time to ship it. A version is a named snapshot of your merged design, and a deployment puts a version into an environment — the place your game connects to. You manage all three from the Deployment menu in the header.

How It Fits Together

  1. Merge a workspace, and Main now holds your changes.
  2. Create a version, which tags Main as it is at that moment.
  3. Deploy the version to an environment. Game clients connecting to that environment receive the version most recently deployed to it.

Creating a Version

Step 1: Open the Deployment Menu

In the header, click Deployment. The menu lists your environments, with the version each one is running, and your versions.

Step 2: Click "Create version"

At the bottom of the menu, click Create version. The Create New Version dialog opens.

Step 3: Fill In the Version

  • Version — a version number in major.minor.patch form, e.g. 1.0.0. It must be different from your existing versions.
  • Description — what the version contains. Required; up to 255 characters of letters, numbers, spaces, underscores, hyphens and periods.

Step 4: Confirm

Click Confirm. Leap confirms "New version created successfully!", and the version appears in the menu.

Important: A version always captures Main's latest merge — even if you create it while you're working in a workspace. Merge your workspace first to include its changes.

Environments

Every project starts with an environment called Dev. Add others as you need them — for example QA or Beta.

  • Add an environment — click Add environment at the bottom of the environments list. Enter a Name (e.g. "QA", "Beta" or "Canary") — letters, numbers, spaces, hyphens or underscores, starting with a letter or number — and click Create. Leap derives the environment's slug from the name; your game uses the slug to connect.
  • Rename an environment — click the pencil ("Rename environment") next to it. Renaming changes the name only: the slug stays the same, so games already connecting to it keep working.
  • Delete an environment — click the bin ("Delete environment") and confirm: "Delete the "{name}" environment? This cannot be undone."

Each environment shows the version it's running, e.g. v1.0.0, or "No version deployed".

Tip: If a project has no environments at all, Leap creates Dev again the next time you open the project.

Deploying a Version

Step 1: Click "Deploy"

In the Deployment menu, click Deploy next to the environment. The Promote Version to {environment} dialog opens.

Step 2: Pick the Version

Under Select Version, choose the version to deploy. The version the environment is already running isn't listed; if there's nothing else to choose, the dialog explains: "Create a new version first."

Step 3: Promote

Click Promote. Leap confirms "Version {version} deployed to {environment}!", and the environment now shows that version.

Going Back to an Earlier Version

There's no separate rollback: deploy the earlier version to the environment again. An environment always serves the version most recently deployed to it.

Your Project's Identifiers

Your project's identifiers are listed in Project settings — open the project menu in the header and click the cog:

  • Identity — your Organization ID and the project's Project ID.
  • Environment — each environment's Name, Slug, Environment ID and Deployed version.

Next Steps

You've reached the end of the guide. Head back to the documentation home to explore any section in more depth.