Skip to content
Agentic Experience Design Language Help Go to the portal

Publish a release

Choose which release Design Language Connect installs and the Connect page offers, and roll back when needed.

For the portal's operators2 min read

On a hosted portal, a new build doesn't reach people's computers the moment it's deployed. It waits under Releases until you publish it, so you decide when Design Language Connect offers an update. You need this after each deployment.

What a release controls

  • Waits for you: the version Design Language Connect installs and offers as an update, and the files the Connect page offers for download.
  • Doesn't wait: the portal's MCP server and llms.txt always serve the deployed design system.

Publish a new release

  1. Go to Operator console › Releases (/operator/releases). The console's Overview also says when one is waiting.
  2. A notice says Design language and the version is deployed. Choose What's new to read its notes.
  3. Choose Publish and the version.
  4. Confirm. Design Language Connect on every computer offers it as an update, and the Connect page's downloads become this release.

Until you publish, Connect keeps offering the release published before. The very first release is published by itself, so Connect always has one.

Some portals are set to publish each build as it's deployed. The Releases screen then says so, and you can still publish an earlier one.

Check what's offered

Offered now shows the published release with:

  • Design Language Connect for Mac, Windows and Ubuntu: each build's version, and whether it's signed (and on Mac, notarised);
  • every file with its size and SHA-256 hash.

Every deployed build lists each build, newest first, with its status: offered now, ready or earlier.

Roll back

  1. Under Every deployed build, find the earlier release.
  2. Choose Roll back and confirm.

New connections and the Connect page get the earlier release. Tools already on a newer version keep it: Connect doesn't downgrade them. Publishing and rolling back are both in the audit log.

The files of the most recent releases are kept, so they can be published again. An older release shows files removed and can't be published.

If something goes wrong

If something goes wrong
What you seeWhat to do
Releases are published on a hosted portalThis portal serves one organisation: Connect gets each build as soon as it's deployed.
A Connect build says not in this buildThat app wasn't included in the deployment. Ask IT to add it and deploy again.
Couldn't publishRead the message, reload, and try again.
A release broke somethingRoll back to the previous one, then publish a fixed build.