AgentKit Studio
Releases and migration

Releases and migration

How the five version numbers compose, which channel a build ships on, and what changes from v0.0.16 backwards — in user-visible terms.

Studio carries five version numbers at once, and they are intentionally not in lockstep. Start here, or every upgrade decision will go wrong.

The five version numbers

VersionCurrent valueUsed byWhat changes when it moves
Plugin version0.0.16package.json#version, the npm packageWhich plugin you install
DSH baseline0.2.2-rc.1studio.plugin.json#requiredDshMust be exactly equal to the running DSH
Host APIdsh-native/0.2.2-rc.1studio.plugin.json#requiredHostApiDSH uses it to admit the plugin
Host contract1studio.plugin.json#requiredHostContractIncrements when the capability surface changes
Desktop version<DSH version>.<YYYYMMDD>.<ordinal>Electron installer and update feedDetermines whether an update can land

Source: package.json:2-3, studio.plugin.json:2-6, src/desktop-release-channels.mjs:14-16.

Desktop versions are not plugin versions

A desktop version looks like 0.2.2-rc.1.20261116.1 — DSH version, build date, and same-day ordinal. Multiple builds in one day therefore become …20261116.1, …20261116.2, and so on. The plugin semver is unaffected.

What this chapter covers

PageQuestion it answersFor
Release notesWhat changed in each versionAnyone deciding "is it worth upgrading"
Version compatibilityPlugin version × DSH baseline × minimum Node × supported platformsAnyone making an upgrade decision
Upgrade to v0.0.16Breaking changes and stepsAnyone already running and moving up
Desktop update channelsFour channels × two feed targets × two layoutsOperators and release engineers

Channels at a glance

ChannelKindAccepts prereleaseNotes
nightlyNative✅Product default
latestNative❌GA lane; three-segment releases only
previewCompatibility✅Historical lane, mirrored on every publication
stableCompatibility❌Historical lane, same comparison rule as latest

Source: src/desktop-release-channels.mjs:20-35,59.

Why is nightly the default? The pinned DSH version carries an -rc.N suffix, and the Studio desktop version inherits it — so every Studio build is a prerelease, and only the nightly native lane accepts those. Once DSH ships a stable release and Studio produces a three-segment version, publishing on latest becomes possible. Source: src/desktop-release-channels.mjs:51-58.

What a release must clear

Source gate

make public-gate

Source audit, secret scan, patch format, package contents, DSH pin, and the full test suite.

Release gate

make release-check

Builds on public-gate with package content validation, patch manifest, and archive integrity.

Desktop artifacts

make desktop-package-preflight
make desktop-package-mac-arm64
make desktop-package-win-x64

Run the preflight first so a version/channel mismatch is caught before signing.

Signing and notarization

macOS signs with a Keychain identity; Windows signs with the Certum certificate. Signing failures are not bypassable — the update path only accepts signed artifacts.

Publish the feed

node scripts/desktop-release.mjs publish

Immutable assets first, feed second. Reversing the order hands clients a 404 update.

Before you upgrade

Your current versionRecommendation
0.0.16Already current, nothing to do
0.0.15Read upgrade to v0.0.16 — there is one real breaking change
OlderGo to 0.0.15 first, then 0.0.16; do not skip multiple versions
UnsureUse the version compatibility table to confirm DSH and Node baselines

On this page