SDK upgrades and compatibility

The product release is 2.0.0-beta.1, the public SDK API version is 2, and the manifest format is schemaVersion: 1. Changing the product’s beta label does not change those protocol numbers.

Upgrade a plugin

1. Use matching SDK/tooling packages.
2. Set apiVersion to 2 and replace removed or incompatible API calls.
3. Keep the plugin ID and compatible setting keys stable.
4. Test persistent-data migrations without deleting user data.
5. Build and pack to regenerate integrity.
6. Import the new artifact and verify that it is disabled pending fresh trust.
7. Enable it and verify behavior, cancellation, and cleanup.

Do not simply change apiVersion on an old bundle. The code must actually use the supported API.

Runtime compatibility

Older installed plugins remain listed but cannot execute when the runtime requires an updated API bundle. Users may need to update the injected runtime before using a new service.

Check selectors against current Fluxer markup as well as SDK types. Structural installation compatibility does not guarantee every plugin’s selector still matches.

Publishing an upgrade

Document new permissions and changes to saved data. Distribute the manifest and matching entry together, preferably as a packager-produced ZIP. The catalog offers bundled updates explicitly; it does not silently replace installed code.