nano v2.0.9
nano v2.0.9 fixes a Valkey issue on multi-node high-availability installs. Single-node and single-app installs are unaffected.
v2.0.9 includes everything in v2.0.8.
To upgrade, follow Upgrade a self-hosted deployment.
Fixes
- Valkey after a server restart (multi-node HA). When the server holding the Valkey primary restarted after a failover, it could act on its own out-of-date view and force a second failover. That briefly created a second primary. For a few seconds Valkey refused writes, and cache and session writes made in that window could be lost. A restarting Valkey server now follows only the primary that a majority of Sentinels agree on, and never forces a failover. Each check of a Sentinel also gives up after 2 seconds, so a powered-off server no longer delays the restart. See High availability.
Who should upgrade
Upgrade if you run a multi-node install with PostgreSQL and Valkey high availability. Single-node and single-app installs are unaffected, but can upgrade as usual.
nano v2.0.10
nano v2.0.10 is the minimum licensed Self-run release. It adds a per-install ID to license check-ins, upgrades from the signed bundle and fixes HEC limits.
nano v2.0.8
nano v2.0.8 includes security fixes, an enforced ingestion pause, a more reliable CrowdStrike FDR source, and install and high-availability fixes.