nano v2.0.25
nano v2.0.25: Evidence Pack compliance exports, an SBOM for every release, and security updates to PostgreSQL, ClickHouse and other components.
v2.0.25 includes everything in v2.0.24. It is a security release. Every self-hosted install should upgrade.
To upgrade, follow Upgrade a self-hosted deployment. v2.0.20 is a required stop: installs on a release older than v2.0.20 upgrade to v2.0.20 first.
New
- Evidence Pack (Self-run). Export the evidence an auditor asks for, for any period, in one step.
- You get three files: JSON, a CSV zip and a PDF summary. The PDF prints the hash of the JSON, and every file carries its own hash.
- It covers log source coverage, detection rules, alerts and how they were handled, access and audit activity, and retention. It holds metadata only, never log content.
- Controls are mapped to SOC 2, ISO 27001, NIS2 and DORA.
- Only users with the
compliance:exportpermission can create packs. Admins have it by default. - The admin guide ships in the release bundle at
docs/administration/evidence-pack.md.
- An SBOM for every release. Each release now has a CycloneDX software bill of materials, attached to the GitHub release and to every image as an attestation. Scan it with a tool like
grypeto check a new CVE against your install. - Scrape a single-host install with your own Prometheus. Set
NANO_METRICS_BIND_ADDRESSto a private address on the host. nano then publishes only its metrics endpoints on that address, still behind the service token. See Monitor your install.
Security
- Updated components: PostgreSQL 17.12, ClickHouse and Keeper 26.10.4, nginx 1.31.8, curl 8.23.0, Prometheus 3.16, Grafana 13.2.6 and Alertmanager 0.35. These bring upstream security fixes, including a code-execution issue in
pg_dumpand authorization fixes in ClickHouse. - Dependency fixes in nano's Rust and npm packages, including TLS certificate handling.
- Narrower ClickHouse network access on Docker Compose. The installer now pins nano's Docker network to one subnet, and ClickHouse accepts nano's users only from loopback and that subnet. Existing installs keep the subnet they already use.
Fixes
scripts/nano upgradecould stop at its last step while Vector was still starting. It now waits until Vector accepts events.- A search using a regex on a numeric field returned an error. It now matches the number's text.
- New ingest tokens could be refused for a few seconds after creation. On a single host, creating a token now waits until it works. On multi-server and Kubernetes installs, the response says when to retry.
Upgrade notes
- Required stop at v2.0.20. See above.
- Run Docker Compose through
scripts/nanoor with the recorded overlays. nano now manages its own network. If you start the stack by hand withdocker compose, include the overlays listed in.envunderNANO_COMPOSE_OVERLAYS. - Kubernetes with your own Prometheus: if Prometheus runs in another namespace, set
vector.metrics.networkPolicyFromso it can reach Vector's metrics. A future release does this for you.
nano v2.0.26
nano v2.0.26: a security and reliability release. Detection rules keep alerting on unusual event data, failures are visible in health, and AI-written searches can't reach the network.
nano v2.0.24
nano v2.0.24 hotfix: Agent Lane works and its port is locked to Agent Lane tokens, single-host upgrades pass preflight, and large parsers deploy on slower hosts.