Releases

Atlas releases are versioned, signed and attested as a unit: one tag produces the binaries, checksums, signatures, provenance and SBOMs for every target, published together. This page describes the release discipline; the artifacts themselves live behind Downloads.

Current release

Every build up to wire 3 carries the single label 1.0.0; 2.0.0 and every later build are numbered under the rules on the Versioning page. Evaluation deployments are expected to track the current line.

3.0.0

• Advert extensions. The signed link-state advert gains an extension area: a map of short keys to values, signed with the rest of the advert. A node keeps every entry it receives, known or not, so an entry it does not know still verifies at the next hop, and it reads only the keys it knows. From wire 5 on, a new advert field goes into the extension area and does not bump the wire; a new top-level field or a changed meaning still does (Versioning, wire versions).
• Bearer kinds, and a one-line summary per peer. The first extension: each node advertises the kind of each of its links (Wi-Fi, Cellular, Ethernet, radio, Bluetooth, mesh, relay, satellite) and whether it is alive. [[link]] bearer = "…" overrides the derivation. The dashboard, atlasd status and the stats API show it as one line per peer, such as phone01: Wi-Fi + Cellular · direct over Wi-Fi; the API carries links[].bearer, members[].bearers and members[].direct_over (API reference).
• Link addresses on the Topology. An optional "addresses" toggle beside the underlying links shows each link's local and remote endpoints as this node sees them now, and follows them when they change, for example as a drone moves between cells.
• The Overview map pane animates open and shut on the "Map" button instead of appearing in one frame.
• Nexus Atlas for Android 3.0.0. Runs on the 3.0.0 core and reports Wi-Fi or Cellular for each of its links. The Activity screen gains a Material level drop-down and a toggle to wrap or unwrap long lines.

2.0.0

• Atlas Interconnect, two modes on one seam. Mapped mode gives each chosen host of the other network an address inside this network's own subnet; prefix mode routes whole prefixes of the other network with their real addresses, through the seam host, with nothing rewritten. Members install the learned routes on their tunnel interface. Concept · Guide.
• Relay discovery that survives a failed map fetch. A node keeps the last signed relay map it verified and attaches from it when the control plane cannot be reached; discovery retries after 5 s, 15 s and 60 s, then every five minutes, and a link attached from the cached map moves only when its relay leaves the map.
• Absent peers, and every member in the stats. A peer counts as absent only when no link of this node reaches it and no member routes to it; a relay link with nobody expected on it no longer counts against the links. /api/stats carries members[]: every node this one knows of, with its state (present, through others, absent), hops, next hop, path cost, links, best RTT and last seen.
• nexus-atlas-relay check. Validates a relay configuration without binding: parses it, reads the private key, checks every address and allowed key, and prints a one-line summary with the relay's public key, the value clients pin as relay_pubkey.
• The host page. GET /api/host on atlasd web describes the machine and every daemon instance on it (host name, kernel, configuration and snapshot directories, each instance's state, uptime, release, unit and relay pins), behind the dashboard's sign-in.
• Mesh views in the dashboard. A member strip on the overview, the Spokes map, Full Topology as one graph of every instance on the host, Timeline rails per neighbour and link, path cards in Mesh & Routes, Fleet tiles per member, and the host page.
• Nexus Atlas for Android 2.0.0. Runs on the 2.0.0 core, installs the routes learned through Interconnect prefix mode, keeps the relay map across restarts, and opens the Activity log full screen with search and filters.

What every release contains

• Static atlasd binaries per target (x86_64 and aarch64 Linux), each with an embedded dependency manifest.
• .sha256 checksums, cosign keyless signatures with certificates, SLSA L3 provenance, and CycloneDX SBOMs — the full set the verification recipe consumes.
• Release notes covering: features and changes, configuration keys added or changed, protocol version implications, any accepted dependency advisories with rationale, and known issues.

Compatibility rules you must plan around

• Protocol version is checked, not negotiated. Every packet carries a protocol version byte; mixed versions fail loudly at decode. Upgrade a deployment as a deployment — release notes flag every protocol-version bump prominently, and mixed-version operation across a bump is not a supported state.
• Configuration is stable-by-schema. The config surface is defined by the daemon's own generated schema (the reference regenerates from it). Deprecated keys keep working with warnings for at least one release line before removal; atlasd config check is the authority on any given binary.
• Wire-compatible opt-ins stay opt-in. Features documented as default-off (traversal, transport classes) do not change the wire behavior of nodes that leave them off.

Release notes & notifications

Release notes are published with each release under Downloads. Organisations with approved access are notified of new releases and of any security-relevant advisory affecting a shipped release at the contact on their access request.