# Releases and pinning

> How SKaaS releases are made, hashed and compared, how an assistant pins one, and how to roll back or withdraw a release.

Source: https://skaas.io/docs/releases
Last updated: 2026-11-14

Every publish is a release, and every release can be pinned. This page covers how a release is identified, compared and withdrawn.

## How is a release identified?

By a content hash. The hash is computed over the list of files: each file's path, content hash, size and executable bit, sorted by path. The same files always give the same hash. Anything that changes a file, adds one or removes one gives a new hash. A release is never edited after it is created.

## How do I compare two releases?

Open a skill in the library, go to its Releases tab and choose two hashes. The viewer shows a file-by-file diff. In the CLI, `skaas update` shows the diff and the audit change before it applies an update.

## How do I roll back?

On your machine, run `skaas rollback <name>`, which restores the release that the last update kept, or `skaas rollback <name> --to <version>` for another one. See [CLI overview](/docs/cli). For everyone who follows a channel, move the channel pointer back to an earlier release, or pin an earlier hash. A release never changes, so a rollback to one that still exists loses nothing. Whether an earlier release still exists depends on the plan: see the next section.

## How many releases are kept?

A release is never edited, but a plan can limit how many of them it keeps for each skill. The retention job deletes the oldest releases beyond the newest N of a skill, and it never deletes a release that is the head of the skill, sits on a channel or belongs to a snapshot. The limits come from the plan table:

| Plan                         | Releases kept for each skill |
| ---------------------------- | ---------------------------- |
| Community, Enterprise        | No limit                     |
| Cloud Free                   | 20                           |
| Cloud Pro                    | 100                          |
| Cloud Team                   | 200                          |
| Cloud Business (not on sale) | 500                          |

Pin a release that you need to keep by putting it on a channel or in a snapshot.

## What is the difference between a yank and a security yank?

A **yank** refuses a release for new installs, and a read that is pinned to its hash still works. A **security yank** refuses every read, pinned or not, and shows the reason. Use a yank for a mistake and a security yank for content that must not be loaded.

Both need admin access and a reason of up to 500 characters. An ordinary yank can be turned into a security yank, and nothing else changes a yank. A security yank raises the organization's policy epoch, which drops cached access decisions. It takes effect at once on the server that handles it and within 60 seconds on every other server. Lifting a security yank needs the admin role. A skill can also be quarantined, which stops every read of every release. See the runbook on withdrawing a release in `docs/runbooks/` of the repository.

## Where did a release come from?

Each release records how it arrived: from the CLI, the API, the web interface, the GitHub App, an import, a sync or an MCP draft. It also records who published it and, when the publisher is an organization that signs releases, a signature over the release hash. See [Signed releases](/docs/signed-releases) and [Publish from CI](/docs/ci-publishing).

## What is stored for each release?

The guide, the supporting files, the manifest of hashes, the provenance and the audit report. The server does not store source paths from your machine.

Public guide and resource responses, including pinned reads, may stay in a shared cache for up to one minute after a security withdrawal or takedown. The origin refuses new reads immediately. There is no cache-purge operation. Recheck a pinned read after that minute.
