build: ldflags version stamp cannot be invalidated by task build's source checksum #1509
Notifications
Due Date
No due date set.
Depends on
Reference: sam/archie#1509
Reference in new issue
Block a user
Split out of archie-core-hhgw (which fixes the ui/dist sources gap). The build task's version stamps are not an input to Task's up-to-date check:
GATEWAY_VERSION / RUNTIME_VERSION (Taskfile.yml:349-353) are computed by
git describe --tags --match ...and passed as -X ldflags. Task'ssources:check is a content checksum over files, so it cannot see HEAD movement or a new tag when no file content changed.Measured on the cp-taskfile worktree at
f600eb01(2026-09-22):describe at HEAD 1.30.0-97-gf600eb01
git commit --allow-empty 1.30.0-98-g0ebf5921 (0 lines of file diff)
task build 'Task "build" is up to date'
bin/archied contains 98-g... 0
bin/archied contains 97-g... 4 <- stale stamp shipped
Why it is not expressible as a sources entry:
What a real fix needs (design decision, not a one-line change): the only in-Task hook for a non-file input is
status:, e.g. persist the describe output next to the binaries during the build andtest "$(git describe ...)" = "$(cat <stamp>)"on the next run. That adds a persisted artifact and deliberately re-links on every HEAD movement (including commits that touch no Go file), so it changes the build task's caching contract and needs its own before/after evidence. Related but distinct from archie-core-k94o (installer-side per-binary version skew detection).Close reason
Fixed in
36118f4e: source builds stamp dev and CI owns the release stamp, so the build cache no longer depends on the commit graph.Imported from beads
archie-core-pdq2· GitHub #1132 · type bug · priority P2 · created 2026-09-21 · closed 2026-09-26