v3.0.0

What's Changed

Breaking Changes

• Node floor raised to >=22.12.0: Amicus 3.0 requires Node 22.12 or later and fails fast with a clear error on older versions. This is driven by @electron/get 5.x (ESM-only), which the Electron self-heal depends on. Node 18/20 users, including headless and council-only users, must upgrade.
• Electron upgraded from 28 to 43.1.1: Drops support for Windows 8/8.1, Windows Server 2012/2012 R2, and macOS 11. The interactive GUI will not run on these platforms; headless runs and the council are unaffected. This upgrade clears the outstanding high-severity npm audit finding (ASAR Integrity Bypass, GHSA-vmqv-hx8q-j7mg).

Features

• Content view migrated from BrowserView to WebContentsView: All four windows now use the modern WebContentsView API and set sandbox explicitly per window, replacing the deprecated BrowserView.
• Early Node version guard: Runtime check fires before heavy imports in bin/amicus.js, so unsupported Node versions fail immediately with an actionable message instead of a confusing error deep in provisioning.

Improvements

• @electron/get upgraded from 2.x to 5.x: Now a direct dependency using ESM. The self-heal defers lazy dynamic import() to the network path and bounds downloads with an AbortSignal timeout (5.x dropped the old got-style timeout interface).
• CI matrices updated to Node 22/24: Aligned with the new Node floor and Electron 43's internal Node 24 runtime.

Known Limitations

• Corporate proxy support requires workaround: @electron/get 5.x uses native fetch, which does not honor HTTPS_PROXY / NO_PROXY environment variables. If you provision Electron behind a corporate proxy, use ELECTRON_MIRROR or manually cache the Electron binary. Headless runs and the council never download Electron.

Full Changelog: v2.2.0...v3.0.0