Update Policy
Update Turboism and its plugins safely, understand background updates, and choose between release channels.
Turboism publishes product releases in three channels and mirrors every package behind a machine-readable release feed. Turboism checks for updates and auto-updates verified first-party plugins in the background, while framework updates remain an explicit step.
Release channels
| Channel | Version shape | Purpose |
|---|---|---|
stable | X.Y.Z | Everyday use. Reviewed release notes and translations. |
beta | X.Y.Z-beta.N, X.Y.Z-rc.N, or X.Y.Z-alpha.N | Try upcoming changes before they are stable. |
nightly | X.Y.Z-0.nightly.BUILD | Daily development builds, produced only when the source changed. |
- 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.
- Since 0.67.0 Stable, each release provides exactly two product downloads:
TurboismInstaller-<version>.exeandturboism-<version>.zip, with matching.sha256checksums. Both include every bundled first-party plugin and the complete offline GraalJS engine. Developer assets (turboism-sdk-<version>.jarandturboism-event-processor-<version>.jar) are published alongside them. - The current Stable release is 0.67.4. The 0.67.0 Beta releases (0.67.0-beta.3 to 0.67.0-beta.7) temporarily used a four-download Full/Thin layout, which is retired. Releases 0.44.0 and earlier used legacy assets (
TurboismInstaller-<version>.exe, the Java installerTurboismInstaller-<version>.jar, andturboism-<version>-full.zip/turboism-<version>-lite.zip). The Java installer is no longer published.
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.jsonA 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
- Back up
config.jsonand any persistent pluginconfig/anddata/content that matters. - Download the newer package for your platform and channel, and verify its SHA-256 checksum.
- Run the newer installer targeting the same Turboism home directory, or replace the files of a portable archive you extracted.
- The installer has no mode or plugin-selection pages. It installs or updates all bundled first-party plugins, retires obsolete official plugin JARs, and keeps existing
disabledPluginsentries disabled. Installations from the retired 0.67.0 Beta Thin installer receive the bundled plugins the same way. - Verify startup, plugin discovery, host capability status, and logs after the update.
Rerunning the installer updates the same home without overwriting unrelated configuration. Do not overwrite or rewrite Cubism installation files as an update mechanism.
Plugin updates and automatic background updates
First-party plugin auto-updates
Since 0.67.0, first-party plugins auto-update in the background:
- The runtime checks for signed first-party updates against the catalog.
- Downloaded updates undergo strict signature and payload verification before staging.
- Plugins marked hot-reload apply immediately to the running session without restarting Cubism.
- Other plugin updates apply the next time Cubism restarts.
- Users can disable automatic first-party plugin updates anytime in framework settings (Automatically update official plugins,
settings.plugins.automatic-updates). - An update is installed only if its declared Turboism API range includes the running framework. Several official plugins require API
0.67.2or0.67.4(see First-Party Plugins); update the framework to receive them. - You can also manually browse, install, or update plugins via Turboism → Plugin Market… or turboism.dev/plugins.
Custom and third-party plugins
Installing a newer plugin JAR with the same plugin ID through Turboism → Manage Plugins… → Install from JAR… stages a replacement intent that applies after Cubism restarts.
- Back up the current plugin JAR and the plugin's persistent
config/<pluginId>/anddata/<pluginId>/content. - Install the newer JAR through plugin management.
- Restart Cubism.
- Verify the displayed version, lifecycle state, configuration migration, and logs.
A failed apply restores the previous plugin files from a private backup.
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 API ranges start at the minimum Turboism framework version a plugin needs and end before
1.0.0(for example[0.67.0,1.0.0)); legacy[0.1.0,0.2.0)plugins are rejected. - Plugin authors should use the declared Turboism API range and test unavailable behavior.
- Plugin management shows each plugin's API range and its declared exact Cubism Editor versions (since 0.67.2).
- The current Stable release 0.67.4 supports all 20 reviewed Cubism Editor versions from 5.0.00 to 5.3.04 (see Compatibility), with Windows x64 as the supported host platform.
Update checker
Turboism checks for stable framework 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.
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 executed automatically. You can also trigger a check manually anytime via the top menu (Turboism → Check for Updates).
The update checker is non-blocking and runs at most once per 24 hours, with a manual check always available. Automatic checks have their own persistent toggle in settings and are independent of Cubism's own update suppression.
Not currently available
- automatic silent execution of framework installers (framework updates require running the installer or extracting the ZIP);
- unverified third-party signature authority;
- retained immutable historical JAR generations;
- a complete user-facing rollback or recovery UI;
- global modification of Cubism launchers.