archie-update-check reads the installed agent version from 'archied -version', which stamps the runtime version the daemon release was CUT with (internal/app/archied.runtimeVersion ldflag), not the version of the managed worker image the installer later rebuilt. After installing archied 1.24.0 and rebuilding the agent image for 1.23.0, /update permanently reports agent installed=1.19.9 available=1.23.0 and re-offers a no-op rebuild every time. Fix: have the installer record the actual installed runtime version somewhere authoritative the check can read (e.g. a version file beside the image, or have the check query the built image labels), instead of trusting the daemon's build stamp.
Close reason
GitHub #856 is closed and the issue's fix is complete; synchronizing Beads with GitHub.
Imported from beads archie-core-e2kn · GitHub #856 · type task · priority P2 · created 2026-09-14 · closed 2026-09-20
archie-update-check reads the installed agent version from 'archied -version', which stamps the runtime version the daemon release was CUT with (internal/app/archied.runtimeVersion ldflag), not the version of the managed worker image the installer later rebuilt. After installing archied 1.24.0 and rebuilding the agent image for 1.23.0, /update permanently reports agent installed=1.19.9 available=1.23.0 and re-offers a no-op rebuild every time. Fix: have the installer record the actual installed runtime version somewhere authoritative the check can read (e.g. a version file beside the image, or have the check query the built image labels), instead of trusting the daemon's build stamp.
### Close reason
GitHub #856 is closed and the issue's fix is complete; synchronizing Beads with GitHub.
---
_Imported from beads `archie-core-e2kn` · GitHub #856 · type task · priority P2 · created 2026-09-14 · closed 2026-09-20_
sam
added the mediumtask labels 2026-10-27 13:39:48 +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.
archie-update-check reads the installed agent version from 'archied -version', which stamps the runtime version the daemon release was CUT with (internal/app/archied.runtimeVersion ldflag), not the version of the managed worker image the installer later rebuilt. After installing archied 1.24.0 and rebuilding the agent image for 1.23.0, /update permanently reports agent installed=1.19.9 available=1.23.0 and re-offers a no-op rebuild every time. Fix: have the installer record the actual installed runtime version somewhere authoritative the check can read (e.g. a version file beside the image, or have the check query the built image labels), instead of trusting the daemon's build stamp.
Close reason
GitHub #856 is closed and the issue's fix is complete; synchronizing Beads with GitHub.
Imported from beads
archie-core-e2kn· GitHub #856 · type task · priority P2 · created 2026-09-14 · closed 2026-09-20