Releases and pinning

Keep a skill and its supporting files together in an immutable release, and choose the exact version an assistant loads.

Prelaunch concept guide

Hosted access and public packages are not open yet.

One release, one content hash

A release contains the guide, supporting files and a manifest of hashes. Its content hash identifies those files. Changing content creates a new release; an existing release is never edited.

Review before changing the pin

An assistant can load a guide and its supporting files pinned to the same release hash. Compare releases and review audit findings before changing the pin. Returning to an earlier retained release restores that version.

Pins do not bypass access or withdrawal

A security withdrawal refuses pinned reads as well as new installs. A pin identifies content; it does not guarantee that content remains available or is safe to use.

How SKaaS works