Update Policy

Turboism publishes product releases in three channels and mirrors every package behind a machine-readable release feed. Turboism checks for stable updates automatically, but installing an update is still an explicit, manual step: no installer is downloaded or executed automatically.

Release channels

• A channel can legitimately report status: not_published; that is an empty channel, not an error.
• Nightly builds are development builds: back up projects before use.
• Every channel produces the same four package formats and the same per-package SHA-256 sidecars.

Machine-readable feeds

Each channel publishes a JSON document:

https://api.turboism.dev/v1/releases/stable.json
https://api.turboism.dev/v1/releases/beta.json
https://api.turboism.dev/v1/releases/nightly.json

A document carries the channel, the selected release (version, tag, buildNumber, sourceRevision, publishedAt), localized release notes, and one row per asset with its name, size, SHA-256, checksum file, and available sources (official mirror and github). Conditional requests are supported. A service error, an empty response, or a failed request must not be treated as “up to date”.

The product website uses the same data for turboism.dev/download.

Update the framework

1. Back up config.json and any persistent plugin config/ and data/ content that matters.
2. Download the newer package for your platform and channel, and verify its SHA-256 checksum.
3. Run the newer installer and target the same Turboism home directory, or replace the files of a portable archive you extracted.
4. Rerun the plugin selection (Full, Thin, or Lite) as part of the update.
5. Verify startup, plugin discovery, host capability status, and logs after the update.

Rerunning the installer updates the same home and selection without blindly overwriting unrelated configuration. Do not overwrite or rewrite Cubism installation files as an update mechanism.

Replace or update a plugin

Installing a newer plugin JAR with the same plugin ID stages a replacement intent that applies after Cubism restarts.

1. Back up the current plugin JAR and the plugin's persistent config/<pluginId>/ and data/<pluginId>/ content when it matters.
2. Install the newer JAR through plugin management.
3. Restart Cubism.
4. Verify the displayed version, lifecycle state, configuration migration, and logs.

A failed apply restores the previous plugin files from a private backup. This workflow does not retain historical generations and does not provide a complete user-facing repair, rollback, or purge UI.

Compatibility expectations

• Turboism publishes one public SDK tier. The reviewed binary API baseline in the source repository is the compatibility gate.
• API presence does not guarantee every Cubism version has a Provider.
• Host-sensitive operations can remain unavailable on unsupported or unverified versions.
• Plugin authors should use the declared Turboism API range and test unavailable behavior.
• Supported Cubism Editor versions are 5.2.03, 5.3.02, and 5.3.03, with Windows x64 as the supported host platform.

Update checker

Turboism checks for stable updates against the deployed release API (api.turboism.dev/v1/releases/stable.json). The comparison uses the authoritative build number embedded in the installed package, so a lower build is never offered as an update and an equal build number with a different version is treated as an identity conflict rather than an update. Installations that predate build numbers keep comparing by version only and are never assigned an invented number.

An available update is presented as a native Cubism hint over the drawing area. Clicking it opens the fixed first-party download page; no URL from the release feed is opened or installed, and no installer is downloaded or executed automatically.

The update checker is non-blocking and runs at most once per 24 hours, with a manual check that is always available. Automatic checks have their own persistent toggle in the Startup settings tab and are independent of Cubism's own update suppression.

Not currently available

• automatic download and installation of framework or plugin updates;
• a production-enabled marketplace;
• publisher signatures and revocation;
• retained immutable JAR generations;
• a complete user-facing repair, rollback, or recovery UI;
• global modification of Cubism launchers.

The built-in Official Directory client and UI exist, but production activation is not ready: the production key list is empty and live signed catalog readiness is not established.