proxy_settings v1.0.2

Polishes the --mitm workflow so a single configure_proxy invocation reliably ends in a coherent state, and updates the release pipeline.

Downloads

proxy_settings-windows-x64.exe — Intel / AMD machines.
proxy_settings-windows-arm64.exe — Windows on ARM (Surface Pro X, Snapdragon-X laptops, etc.).

MITM CA is now generated before the daemon starts. Previously the daemon generated its own CA after binding its port, opening a small race where the bundle write that followed could miss the file. The parent process now pre-generates the CA so the daemon just loads an existing file.
A CA bundle is now written when --mitm is in use even if no corporate inspection cert is detected. Previously this silently produced a half-broken state — the MITM CA was generated but never landed in any trust bundle, so Git/npm/Node had no way to trust the local interception.
Removed a misleading "MITM CA not in Node bundle" warning from the daemon startup log. The daemon process inherited its environment before setx could update NODE_EXTRA_CA_CERTS, so the warning always fired on first run regardless of whether the parent was about to fix exactly that. The same diagnostic is still available on demand via auth_proxy.py --mitm-check, where the surrounding shell env makes the result meaningful.
Clearer error when --mitm is requested without cryptography installed (source installs only — the .exe bundles it). Exits with a one-line install hint instead of a partial setup.

Build script honors the Python version actions/setup-python requested. The interpreter-detection loop preferred the Windows py launcher, which always picks the latest installed Python on the system; on the ARM64 runner that landed on 3.14.4 even though the workflow asked for 3.13. Cryptography doesn't yet ship a 3.14 Windows ARM64 wheel, so the ARM64 build fell back to compiling OpenSSL via Rust and failed. The script now searches python → python3 → py, so the version setup-python puts at the head of PATH wins.
Release workflow updated to Node.js 24-compatible action versions (actions/checkout@v5, actions/setup-python@v6, actions/upload-artifact@v5) and sets FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true to cover any action that hasn't shipped a Node 24 release yet. Silences the deprecation warnings.

Full Changelog: v1.0.1...v1.0.2

Full Changelog: v1.0.1...v1.0.2