Topline Docs

Artifacts

Artifact publishing and rollback

Publish the reviewed version, verify live status, and restore a prior live version when needed.

Artifact publishing and rollback

Publish the reviewed version, verify live status, and restore a prior live version when needed.

Where to find it

Open Apps & Workspaces, choose the workspace, and open the artifact. Its header and drawers contain the settings for this guide.

Address: /artifacts/:id. Open the saved resource from the product rather than typing this address.

Publish an app

  1. Open Apps & Workspaces, choose the owning workspace, and open the app.
  2. Create or update its private draft through a Topline coding task or Build MCP. Ask for a deployed, validated draft and an operator review link.
  3. Review the draft, its data and secret bindings, rendered pages, and required acceptance checks. Open App access and check its Publishing section. When publishing is blocked, Publishing details opens automatically and lists the app status, App readiness, deployment evidence, and publish blockers. A blocked status in the page header, such as Smoke checks required, opens the same place. Resolve any deployment or validation blockers before continuing; use the offered fix button, such as Start app validation, Continue app validation, or Fix with Coding agent, when one appears.
  4. Use Publish vN in App access > Publishing for the reviewed version. If the control is unavailable, finish the required checks rather than changing sharing settings to try to bypass the blocker.
  5. Confirm that App access reads Live · vN for the intended version. Open the app with Open app in the page header and check its main workflow. Keep the prior reviewed live version available for rollback; Roll back is under Publishing details.
  6. As the artifact owner, use App access and Topline access to configure the audience using the live access and Topline access guides. An editor can publish when permitted, but changing sharing remains an owner action.

A source commit, successful build, deployed private draft, passing HTTP check, or Storybook story is not proof of live promotion. A shared-platform deploy is also distinct from customer-runtime rollout. Build MCP deploys private drafts; live promotion remains an operator action in Topline.

Hosted MCP server artifacts add a connection-review step after promotion. See Build a hosted MCP server.

Roll back

Open Publishing details and use Roll back when an eligible prior version is available. Review the intended version and verify the live result after the action. Reverting source or deleting an artifact is not a substitute for changing its live version.

Sharing is a separate step

After confirming the intended version is live, choose the audience in App access. Publishing does not automatically make the app public or add recipients. For a non-app artifact, inspect Link access and the published-link controls available for that artifact type.