Updates

Plinken Run is updated separately from the web app. The app checks the published version list each time it talks to a runner and tells you when yours is behind.

Where you see it

• Settings → Runner: “Update available: version X” appears on the card, with the downloads listed below.
• Native Engine page (right-click the header runner button → Engine…): the same notice with more detail.
• When no update is available, nothing is shown.

Installing an update

Install the new version the same way you installed the first one:

1. Download the new build from Settings → Runner (or the stable links on the macOS and Windows pages).
2. Quit Plinken Run (close its window, or ⌘Q / Ctrl+Q).
3. macOS: open the .dmg and drag Plinken Run to Applications, replacing the old copy. Windows: extract the zip over the old plinken-run.exe (unblock it first).
4. Open Plinken Run again and reconnect.

Your plugin preferences and caches under ~/.plinken/ are kept.

The Update button on the card downloads and verifies the new build into ~/.plinken/cache/updates/, but it does not install it yet. Even after the app reports the download as finished, quitting and reopening Plinken Run keeps the version you had. Install from the download as above.

Minimum supported version

Each release of the web app names the oldest runner it still works with. A runner below that floor is refused: the card reads “This runner is below the minimum supported version (X). Update to continue.” and the app does not connect. Update the runner and reconnect.

The same applies when the video pipeline version differs between app and runner: video jobs are refused until the runner is updated. See Video with Plinken Run.

Offline

If the version list cannot be reached, for example on a LAN without internet, the app skips the check and the runner connects as normal.