You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
The Upgrade button now sets itself up. Enabling dashboard.control is all
it takes: ./stack up/apply start the host-side upgrade-agent detached
(log: ~/upgrade-agent.log) and install a @reboot cron entry so it survives
reboots — no sudo, no unit file. Disabling control and re-applying stops the
agent and removes the cron entry. If the documented systemd unit is enabled,
the stack defers to it. ./stack init asks one new question ("One-click
upgrades from the dashboard?", default no), and ./stack doctor reports
whether the agent is running.
Sandboxed lifecycle tests for the agent manager.test_cli.sh stubs crontab/docker/pgrep/pkill/setsid/systemctl onto PATH and drives
enable → re-apply (idempotence) → disable → systemd-deference without
touching the host. The suite immediately caught a pipefail crash in the
disable path when the agent's entry was the only crontab line.
Changed
README: the feature list now covers one-command upgrades, the daily update
check, and the Prometheus /metrics endpoint; the Testing section describes
the full suite (including the e2e Tor-only egress audit and the gitleaks /
hadolint CI jobs).
Fixed
CHANGELOG version headings 1.23.0–1.29.1 had no reference links, so they
rendered as literal brackets on GitHub.