task build does not stamp installtype, making task-built binaries un-updatable #1168
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#1168
Reference in new issue
Block a user
Symptom: /update in Telegram on carina fails with 'refusing to install: install type is unknown'. Cause: internal/installtype.buildType must be stamped at build time (-X .../internal/installtype.buildType=binary); releaseupdate.Service.InstallType is wired from installtype.Type() and Install deliberately refuses when it is Unknown. Taskfile.yml's dev build task (lines ~454-459) passes the stamp ldflags for archied, archie-gateway and archie-agent but NOT for archie-messaging, archie-state-store or archie-ui. install.sh (~line 176) and .github/workflows/deploy.yml (~line 257) both stamp correctly, so any binary installed from 'task build' is permanently un-updatable and the failure only appears when an operator tries to update. Found 2026-09-22 after a hand-built archie-messaging (built to fix the Telegram outage) made /update refuse on carina. deploy.yml:253 already carries a comment about this same class ('...and nothing added archie-messaging here, so a host install...'). Fix: stamp every cmd in the build task, and stop the next person hand-building a distribution binary.
Close reason
Fixed by
3d08560b: task build stamps installtype.buildType=binary (plus version flags) on every distribution binary; verified with go version -m on all six.Imported from beads
archie-core-8kom· GitHub #1039 · type bug · priority P1 · created 2026-09-22 · closed 2026-09-27