Released binaries report dev instead of the release version #104
Labels
No labels
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agent-compose#104
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The Scoop-installed
agent-composev0.61.0 reportsdevfromagent-compose version. The package manifest, downloaded release, and installed flags are current, so the released binary is present but its linker-injected version is wrong.Evidence
acompose --helpincludes the v0.61.0 flags.agent-compose versionprintsdev.scripts/release-build.shstamps-X main.version=${VERSION}. The Homebrew formula tests the runtime version, but the Scoop manifest has no equivalent assertion.Needed
Reproduce the release build at an exact tag through Ward, correct the linker target or version input, and add a release-asset assertion that executes each binary where practical. Ops then verifies the next normal release reports its tag after package-manager installation.
Closing as a false alarm. PowerShell resolved gent-compose to an older development build in $GOBIN, while compose resolved to the Scoop installation. Executing the v0.61.0 Scoop asset directly reports 0.61.0, so release stamping is correct. The remaining condition is local PATH shadowing, not a release defect.
Correction to the formatting above: PowerShell resolved agent-compose to an older development build in $GOBIN, while acompose resolved to the Scoop installation. The Scoop v0.61.0 executable reports v0.61.0. Version stamping is correct, and local PATH shadowing caused the misleading result.