Skip to main content
Releasing a skill version makes it the version Atlan Trident serves, so the people and agents using the skill get your changes. Use it when your workspace’s release policy holds saved versions until someone releases them, or when you need to roll back or withdraw a release. Whether a saved version ships on its own is the workspace’s release policy, which a workspace admin sets; see Set workspace release policy.

Before you begin

Before you start, make sure you have:
  • Permission: You own the skill or are a workspace admin. Only the skill’s owner or a workspace admin can release it. An archived skill can’t be released, and a skill installed from the Store can’t be either: it has no Releases tab, its updates come from the Store, and its versions are on Source.
  • Saved version: A version saved after the current release whose checks have finished.
1

Open skill versions

Open the skill and select Releases. The versions list shows Live beside the version Atlan Trident serves, Checking or Blocked beside a version its checks hold back, and Not released yet when nothing is released. When a newer saved version isn’t released, the profile header shows Unreleased changes.
2

Prepare release

Select Release beside the newest version. It appears only when the workspace’s release policy is Manual, the version’s checks have finished, and it isn’t already live. The Prepare release dialog opens.Choose the Release version, and review Release notes (optional): add why the changes were made.When the release policy allows public releases, the dialog also asks Who can use it. This organization keeps the release private: a Store listing can offer it to named organizations only. Every Atlan customer makes it public: a Store listing can offer it to every Atlan customer. The choice starts on the workspace’s default visibility. The Releases page marks a public release with a Public badge.A version ships only once on a channel. If the version you choose has already shipped on this channel, even if you withdrew its release earlier, the dialog refuses it and tells you to save a new revision to release again. To reuse an earlier package instead, use Restore as new version; to serve the release before the current one again, use Roll back to.
3

Publish release

Select Publish; the button names the version. If a release is already queued, the button reads Replace and publish and replaces that queued release.
4

Verify release

In the versions list, confirm that Live now sits beside the new version and that the header no longer shows Unreleased changes. To see releases across workspaces, open Releases from the More actions menu on a workspace’s or your organization’s page.
5

Roll back or withdraw (optional)

Open the menu on the Live version, or on a queued one:
  • Roll back to: Serve the release before the current one again.
  • Withdraw release: Shown when nothing was released before it. Nothing is served for the skill afterwards.
  • Withdraw queued release: Cancel a release that hasn’t shipped yet.
To reuse an earlier package instead, select Restore as new version on that version. Restore creates a new version and keeps history intact. See How skill versions and releases work.

Troubleshooting

If a version is blocked by its security scan, see Security scan blocked skill.

Next steps

See also