Skip to main content
Every save to a skill creates a version, and a version reaches people and agents only once it is released. This lets a skill change without changing what your team already uses, and lets you return to an earlier release when a change goes wrong.

Saved versions

A version pins the skill’s files, so its instructions and supporting files can be reconstructed later. Each version has one state: In the versions list on Source, a released version is marked Live and one in review is marked Checking. Version history makes usage easier to read: a run attributed to version 2 can be compared with the exact files that were released for it, even after version 3 replaces it.

Releases and policy

The workspace’s Publishing policy, which a workspace admin sets, decides how a saved version is released:
  • Automatic: Each saved version is released once its required checks pass.
  • Manual: A saved version waits until the skill’s owner or a workspace admin releases it from the versions list on the skill’s Source tab.
Only the skill’s owner or a workspace admin can release a version, roll back, or withdraw a release. A skill with no owner can be released only by a workspace admin.

Restore and roll back

Both keep history intact:
  • Roll back to serves the release before the current one again. If nothing was released before it, Withdraw release is offered instead, and the skill then serves nothing.
  • Restore as new version copies an earlier version’s files into a new version. Under Automatic, it is released once its checks pass; under Manual, the current release stays until someone releases the new version.
Withdrawn releases stay on the record.

Where versions and releases appear

  • Source tab: Every version with its state, author, and date, with Live beside the one Atlan Trident serves and the Release, roll back, and withdraw actions. Open an earlier version to select Compare with vN or Restore as new version. The profile header shows Unreleased changes when a newer saved version isn’t released.
  • Releases page: Queued, released, and withdrawn releases across workspaces. Open it from the More actions (⋯) menu on a workspace’s or your organization’s page.

Example

meeting-notes-to-actions lives in a workspace with a Manual policy. Version 3 is Released. The author saves version 4, which passes its scan and shows Unreleased. The owner releases it, and a day later a reviewer reports a regression, so the owner selects Roll back to version 3. Version 4 stays in history, and the author later fixes it as version 5.

What versions do not do

  • Saving does not release. Under Manual, people keep getting the current release until someone releases the new version.
  • Restore does not rewrite history. It adds a new version; the versions between stay on the record.
  • Compare is against the newest version only. To compare two earlier versions, open each in Source.