Update Policy

Turboism currently has local JAR replacement and manual installer reruns, not a production automatic update system.

Plugin replacement today

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

1. Back up the current plugin JAR.
2. Back up persistent config/<pluginId>/ and data/<pluginId>/ content when it matters.
3. Install the newer JAR through plugin management.
4. Restart Cubism.
5. Verify 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.

Framework installer updates

A newer framework version is installed by rerunning an installer package:

1. Obtain the newer TurboismInstaller-<version>.exe (Windows) or TurboismInstaller-<version>.jar (Windows/macOS) from the release or preview channel that provided your build.
2. Back up config.json and any persistent plugin config/ and data/ content that matters.
3. Run the newer installer and target the same Turboism home directory.
4. Rerun the plugin selection (Lite/Full) 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. There is no automatic online updater and no signed public download channel yet; installer updates are manual reruns. Do not overwrite or rewrite Cubism installation files as an update mechanism.

Compatibility expectations

• New SDK APIs are Preview by default.
• 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.
• The generated API reference tracks current development source, not a final Stable release line.

Not currently available

• production online update discovery and downloads;
• marketplace channels;
• publisher signatures and revocation;
• retained immutable JAR generations;
• a complete user-facing repair, rollback, or recovery UI;
• automatic system-level installer updates;
• a published Stable compatibility matrix.

The built-in Official Directory client and UI exist, but production activation is not ready: the signed endpoint and key readiness are incomplete.