Versions and publishing

An artifact is a series of versions. Each version is a complete set of files with a number like 1.4.0 (major.minor.patch, plain digits, no v and no labels such as -beta).

Versions only move forward

A new version must be higher than every version the artifact already has, including rejected ones. Once a version is published it never changes: to fix something, publish a new version. This is what makes an install or a review mean something.

Publish a new version

• From the artifact page, press New version to upload a fresh SKILL.md.
• Or open the artifact's publish page (its address followed by /publish), press Select files, enter a Semver version and a note, tick any open issues it fixes under Closes issues, and press Publish version.
• From a terminal, run deftro publish in the skill folder.

In a personal account the version is published at once. In an organisation it usually waits for Review first.

History and Compare

The History tab lists every version, newest first, with its status (published, in review, rejected, withdrawn or yanked), release note, author and Health check score. Tick two versions and press Compare diff to see every changed file line by line.

Yank a version

If a published version is broken or harmful, press Yank, give a reason, and press Confirm yank. Yanking blocks new installs and alerts everyone who installed it. It cannot remove the files from their machines. You then see how many people and machines had it, with a link to the install ledger.

In a personal account only the owner can yank; in an organisation it depends on your role.

Restore an old version

Press Restore on any version that is not yanked, choose a New version number, and press Restore version. This publishes a new version with the old files; the old version itself is not touched. In an organisation the restored version goes through Review like any other. A yanked version cannot be restored: publish a new version instead.