The update command is not responsive enough during an update. The UX is excellent up to the point where the update starts, but then it does not clearly communicate whether the update succeeded, which version is now running, or whether the daemon and agent were updated successfully.
A failed update also requires manual intervention instead of automatically restoring the previous known-good installation.
Desired behaviour
When an update is requested, show progress/status throughout the operation, including:
update requested and started
current version and target version
download/build/install stages
daemon update status
agent update status
restart/health-check status
final success or failure state
On success, show a concise summary containing:
previous version
installed version
components changed (daemon, agent, and any other updated components)
whether the health check passed
On failure:
automatically roll back to the previous known-good version
restore/restart the daemon and agent as needed
verify the rollback with a health check
report the failure, rollback result, and versions to the user
Acceptance criteria
The command provides visible progress while the update is running.
The final response explicitly states success or failure.
The final response includes the previous and resulting versions.
Daemon and agent update/restart outcomes are reported separately.
Failed updates roll back automatically without manual intervention.
Rollback is health-checked and its result is reported.
Shipped in archied v1.9.10 (commit 95290d1, feat(update): stream live progress and roll back failed updates automatically) -- live progress reporting, version summary, and automatic rollback on failed updates all landed and released.
Imported from beads archie-core-1786748942495-16-0d6ea565 · GitHub #511 · type feature · priority P1 · created 2026-08-14 · closed 2026-08-18
## Problem
The update command is not responsive enough during an update. The UX is excellent up to the point where the update starts, but then it does not clearly communicate whether the update succeeded, which version is now running, or whether the daemon and agent were updated successfully.
A failed update also requires manual intervention instead of automatically restoring the previous known-good installation.
## Desired behaviour
When an update is requested, show progress/status throughout the operation, including:
- update requested and started
- current version and target version
- download/build/install stages
- daemon update status
- agent update status
- restart/health-check status
- final success or failure state
On success, show a concise summary containing:
- previous version
- installed version
- components changed (daemon, agent, and any other updated components)
- whether the health check passed
On failure:
- automatically roll back to the previous known-good version
- restore/restart the daemon and agent as needed
- verify the rollback with a health check
- report the failure, rollback result, and versions to the user
## Acceptance criteria
- [ ] The command provides visible progress while the update is running.
- [ ] The final response explicitly states success or failure.
- [ ] The final response includes the previous and resulting versions.
- [ ] Daemon and agent update/restart outcomes are reported separately.
- [ ] Failed updates roll back automatically without manual intervention.
- [ ] Rollback is health-checked and its result is reported.
- [ ] Existing update deferral/check behaviour remains intact.
- [ ] Tests cover successful updates, failed updates with successful rollback, and rollback failure.
## Related
- #359 — Telegram: announce newly installed Archie releases
### Close reason
Shipped in archied v1.9.10 (commit 95290d1, feat(update): stream live progress and roll back failed updates automatically) -- live progress reporting, version summary, and automatic rollback on failed updates all landed and released.
---
_Imported from beads `archie-core-1786748942495-16-0d6ea565` · GitHub #511 · type feature · priority P1 · created 2026-08-14 · closed 2026-08-18_
sam
added the highfeature labels 2026-10-27 13:38:30 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
The update command is not responsive enough during an update. The UX is excellent up to the point where the update starts, but then it does not clearly communicate whether the update succeeded, which version is now running, or whether the daemon and agent were updated successfully.
A failed update also requires manual intervention instead of automatically restoring the previous known-good installation.
Desired behaviour
When an update is requested, show progress/status throughout the operation, including:
On success, show a concise summary containing:
On failure:
Acceptance criteria
Related
Close reason
Shipped in archied v1.9.10 (commit 95290d1, feat(update): stream live progress and roll back failed updates automatically) -- live progress reporting, version summary, and automatic rollback on failed updates all landed and released.
Imported from beads
archie-core-1786748942495-16-0d6ea565· GitHub #511 · type feature · priority P1 · created 2026-08-14 · closed 2026-08-18