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
{{ message }}
Repository navigation
Detailed per-Machine version and upgrade reporting command #605
Follow-up decided while grilling #601. The enroll fix makes CLI/daemon skew self-healing on the Cloud path, and machine ls gains a footer warning on skew — but there is no surface that answers, per Machine: which daemon version is installed, how it compares to the CLI and to the latest release, and what an upgrade would do.
Relationship to existing work
#462's CLI tree already specs ployz doctor ("missing Docker CLI, Compose plugin, SSH agent, or version skew is diagnosed here"). Doctor covers diagnosis. This issue covers the upgrade-detail half: per-Machine version inventory and upgrade guidance (what would change, in what order, whether a Machine needs re-enrollment or just a binary swap).
Direction
A ployz version-style command (exact placement to be reconciled with the #462 tree) reporting per-Machine daemon versions, CLI version, skew, and available upgrades. Read-only; acting on upgrades stays out of scope.
machine ls already shows each Machine's daemon version and warns on skew (#609), machine upgrade shipped in #827, and #1212 (#1214) removed version and put the latest upgrade attempt on machine inspect. "A newer release is available" belongs with Cloud upgrades (#826).
Activity
nick-potts commentedon Sep 29, 2026
machine lsalready shows each Machine's daemon version and warns on skew (#609),machine upgradeshipped in #827, and #1212 (#1214) removedversionand put the latest upgrade attempt onmachine inspect. "A newer release is available" belongs with Cloud upgrades (#826).