Release Notes

Release Notes record stable-release changes that affect deployment, upgrades, configuration, APIs, and runtime behavior.

Prereleases are not documented separately. Changes from prerelease builds are folded into the matching stable release.

Dash

Released: 2026-06-17

GitHub Release: Ithiltir 0.2.6

The Dash updater adds the reinstall command. It reinstalls the latest package from the selected channel even when the installed version already matches the target version.
Bundled /deploy/* node binaries and runner assets are protected downloads. Normal requests require X-Node-Secret; legacy node upgrades use a short-lived upgrade_token generated by Dash.
Node automatic update handling supports SemVer build metadata. Node binaries with the same SemVer precedence but different build metadata can still be delivered.
Linux node install scripts support Chinese and English output.
The Linux node install script compiles a root-side connections cache helper when cc, gcc, or clang is available. The helper counts TCP/UDP connections in host and container network namespaces.
Runtime metrics and historical metrics have clearer storage boundaries. TCP/UDP connection counts remain historical numeric metrics. SMART, thermal, and full runtime details stay in current snapshots or frontend caches.

Legacy node upgrade downloads receive a temporary authorized URL when they cannot send X-Node-Secret.
Updating a node secret to one already owned by another node returns 409 duplicate_secret.
Frontend cache rebuilds no longer depend on the cancellation state of the initiating request.
Dash closes the underlying server after a failed graceful shutdown.

Prereleases are not listed as separate Release Notes entries.
The minimum node version for automatic update delivery from the Dash admin console remains 0.2.1.
Install script templates under /deploy/* remain public. Bundled node binaries and runner assets require authentication.
Back up the database before production upgrades. The release-package updater runs migrations; manual binary replacement requires manual migration.

Released: 2026-06-17

Node sends the current target key as X-Node-Secret when downloading assets from an update manifest.
Linux and macOS managed install layouts switch /var/lib/ithiltir-node/current after staging an update, then exec the updated node with the original arguments and environment.
Windows managed installs use the runner to replace the binary and restart node after staging an update.
Install layouts that do not support self-update report self update disabled and continue the reporting loop.
On Linux, node keeps its built-in connection counting fallback when the connections cache is missing, stale, or unavailable.

Fixed staged updates that did not restart correctly or did not execute the updated binary.
Fixed authentication handling for protected update asset downloads.
Fixed connection counting fallback behavior when the connections cache is unavailable.

Windows self-updates require runner-managed installs.
Linux and macOS self-updates require the /var/lib/ithiltir-node/releases/<version> and /var/lib/ithiltir-node/current install layout.
Direct binaries outside the managed install layout do not apply update manifests. Rerun the install command or replace the binary manually.