Release v0.65.7
May 08, 2026
Fixes a Windows installer regression, restores agent auto-update, and adds a recovery path for fleets that got stuck on v0.65.5 or v0.65.6.
Improved
- Self-hosted deployments now have the required production environment variables (public API URL, force-HTTPS, trusted proxy CIDRs) wired through the bundled docker-compose files, so a fresh install boots cleanly without the API rejecting startup with a configuration error.
- Bumped the Go runtime used to build the agent to 1.25.10, picking up upstream security fixes.
Fixed
- Restored agent auto-update. A wrong signing key was embedded in v0.65.5 and v0.65.6 agents, which caused every signed release manifest to fail verification and silently parked agents in an "updating" state without ever completing. The correct key is now embedded, and a server-side recovery script is included for operators who need to rescue agents that are still stuck on v0.65.5 or v0.65.6.
- Fixed Windows MSI installs failing with a generic 1603 rollback on fresh machines. The folder-hardening step ran before the folders existed and used a path quoting form that broke the underlying command line. Both issues are resolved; clean installs now finish without rollback and apply the intended ACLs.
- Fixed the dashboard saving downloaded Windows installers as the wrong filename. The download flow now reads the server-supplied filename and falls back to a sensible default, so Windows installer downloads save as a ZIP archive instead of an MSI with the wrong contents.
- Removed two coturn flags from the bundled compose configs that don't exist in any released coturn image and prevented the relay container from starting. Loopback peer denial — the protection those flags were originally added for — is preserved by the explicit IP range rules already in place.
- Corrected Windows service names in the documentation. The on-disk services register as BreezeAgent and BreezeWatchdog; older docs referenced the lowercase forms, which made the manual service commands fail.
This release fixes the agent auto-update loop that left fleets stuck on the previous two releases. If you noticed agents reporting “updating” indefinitely after v0.65.5 or v0.65.6, this is the fix — and there’s a one-command recovery path on the server side so operators don’t have to touch each affected machine.
It also unblocks fresh Windows installs that were failing with a 1603 rollback on first run. Both bugs in that installer have been fixed and verified end-to-end on a clean Windows Server 2022 VM.
A handful of smaller cleanups round out the release: corrected Windows service names in the docs, removed two coturn flags that didn’t exist in the released image, and a wiring fix for required production environment variables in the self-hosted compose file.