Skip to content

v0.0.10 — all three installers at the same level

Choose a tag to compare

View all tags
@an80sPWNstar an80sPWNstar released this 19 Aug 00:32
· 12 commits to main since this release
v0.0.10
9053633

Windows, Linux AppImage and Linux deb are all cut from the same commit for the first time since 0.0.7. No new features — this release exists to close the gap.

What was out of step

  • The 1s VRAM poll landed right after the 0.0.9 exe was built, so the relay bundled in that installer still refreshed the VRAM row every 2 seconds and visibly lagged nvidia-smi. It polls once a second here (still 2s on hosts without pynvml, where every read costs a subprocess).
  • Linux stayed at 0.0.7. WSL2 stopped starting on this machine on 2026-08-16 and the AppImage/deb could not be built for 0.0.8 or 0.0.9. Virtualization is back, so both Linux artifacts skip straight to 0.0.10 and now carry everything from those two releases:
    • Electron 31 (end-of-life) → 43, electron-builder 25 → 26
    • VRAM read through NVML the way nvitop reports it, including the v2 memory struct so driver-reserved memory is not counted as used
    • the workflow-stage NODE line, with subgraph-expanded node ids collapsed to the node you actually see on the canvas
    • reactor dial figure clear of the arcs

Installer payload (why the .exe is ~8 MB bigger than it first was)

These artifacts were rebuilt on electron-builder 26.15.7. Under 26.15.3 the bundled 7za applies the BCJ2 filter to executable content, which the Nsis7z extractor inside the installer cannot decode — an install can silently drop the main .exe and every DLL and still report success (electron-builder #9983). This project's installers were not affected in practice, but 26.15.7 pins the payload to single-stream BCJ so it cannot happen; the archive compresses a little worse as a result.

Verified before publishing

  • npm test 5/5. npm audit: 0 vulnerabilities.
  • The ComfyUI node pack ships as a resource, so its contents were hashed inside each package: the exe, the AppImage and the deb all carry a relay byte-identical to the repo.
  • The Windows installer payload was unpacked and inspected — no BCJ2 block remains.
  • The packaged Windows build was launched (ProductVersion 0.0.10.0, window up), not just checked for a zero exit code.

Installing the ComfyUI node pack is still the one manual step: copy resources/comfyui-relay/ into your ComfyUI custom_nodes/ and restart. The app's (i) panel prints the path and opens it for you.

Assets 5
Loading