fix(update): install only approved changed components #989

Closed
opened 2026-10-27 13:38:35 +00:00 by sam · 0 comments
Owner

Bug Description

A gateway-only /update (archied/v1.13.0 while runtime remains archie/v1.9.9) fetches and builds both binaries, backs up and installs both, and rebuilds the agent image. The image build does not receive RUNTIME_VERSION, so the released runtime is stamped dev.

Steps to Reproduce

  1. Run /update with only the daemon component available.
  2. Approve the displayed snapshot.
  3. Observe archie-update-install build/install both components and run docker compose build agent.

Expected Behavior

The approved snapshot flows into CommandInstaller; only changed components are fetched/built/backed up/installed. Rebuild the agent image only for a runtime update and stamp it with the released runtime version. Preserve phase-1 result and phase-2 rollback/report metadata for gateway-only, runtime-only, both, and no-op plans.

Actual Behavior

The installer receives only chat/report metadata, so the script independently rebuilds everything after git pull and Docker uses its default RUNTIME_VERSION=dev.

Acceptance Criteria

  • Regression harness proves a gateway-only update never builds/installs the runtime or image.
  • Tests cover gateway-only, runtime-only, both, and no-op.
  • Released runtime images are stamped with the release version, never dev.
  • Rollback/report metadata remains component-aware and correct.
  • task check passes.

Imported from beads archie-core-1787522397925-3-87bd827d · GitHub #606 · type bug · priority P2 · created 2026-08-23 · closed 2026-08-23

## Bug Description A gateway-only `/update` (archied/v1.13.0 while runtime remains archie/v1.9.9) fetches and builds both binaries, backs up and installs both, and rebuilds the agent image. The image build does not receive `RUNTIME_VERSION`, so the released runtime is stamped `dev`. ## Steps to Reproduce 1. Run `/update` with only the `daemon` component available. 2. Approve the displayed snapshot. 3. Observe `archie-update-install` build/install both components and run `docker compose build agent`. ## Expected Behavior The approved snapshot flows into `CommandInstaller`; only changed components are fetched/built/backed up/installed. Rebuild the agent image only for a runtime update and stamp it with the released runtime version. Preserve phase-1 result and phase-2 rollback/report metadata for gateway-only, runtime-only, both, and no-op plans. ## Actual Behavior The installer receives only chat/report metadata, so the script independently rebuilds everything after `git pull` and Docker uses its default `RUNTIME_VERSION=dev`. ## Acceptance Criteria - Regression harness proves a gateway-only update never builds/installs the runtime or image. - Tests cover gateway-only, runtime-only, both, and no-op. - Released runtime images are stamped with the release version, never `dev`. - Rollback/report metadata remains component-aware and correct. - `task check` passes. --- _Imported from beads `archie-core-1787522397925-3-87bd827d` · GitHub #606 · type bug · priority P2 · created 2026-08-23 · closed 2026-08-23_
sam added the mediumin-progressbug labels 2026-10-27 13:38:35 +00:00
sam self-assigned this 2026-10-27 13:38:35 +00:00
sam closed this issue 2026-10-27 13:38:35 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#989