Update FluxPlugs and plugins

There are three different updates: the FluxPlugs injector, the runtime injected into Fluxer, and individual plugins.

Update FluxPlugs and its runtime

1. Get the newer injector:
   • Downloaded build: download the newer release as described in Download the injector. The Windows installer and the deb and rpm packages install over the old version. For the AppImage, replace the old file.
   • Source build: pull the newer source revision, preserving any local changes, then run pnpm install –frozen-lockfile and pnpm build from the project root.
2. Launch the injector, scan, and select your installation.
3. Choose Check status, then Update injection.
4. Review the new preview and confirm it. Allow the injector to close and relaunch Fluxer.

The injector’s Check for updates button is currently a placeholder. It doesn’t download releases or perform these steps.

Update plugins

Import an updated plugin ZIP or manifest. For bundled plugins, use Update when a newer catalog entry is offered.

Compatible setting values and separate plugin storage are retained. Changed code is disabled until you confirm its new hash and permissions. Updating the catalog does not silently overwrite installed plugins.

After Fluxer updates itself

Each Fluxer update replaces the files FluxPlugs modified, so FluxPlugs stops loading until you inject again. Installed plugins, their settings and their storage are not affected.

1. Run a new scan and choose Check status.
2. If the status reads Re-inject needed, the backup shows From previous Fluxer version. It belongs to the old build and is replaced when you inject.
3. Review the injection preview and confirm it.

If the status reads Recovery required instead, the files changed in a way that doesn’t look like an update. Don’t inject over it; reinstall Fluxer first. An update can also change Fluxer’s structure so the installation is no longer supported; only proceed with the operations the injector allows.

If the UI says the plugin needs a newer API, update the injected runtime as well as the plugin bundle. The product version and SDK version are separate.