Skip to content

Rename the binary to aixgo-code; the framework owns aixgo - #143

Merged
charlesgreen merged 1 commit into
mainfrom
fix/binary-name-collision
Aug 9, 2026
Merged

Rename the binary to aixgo-code; the framework owns aixgo#143
charlesgreen merged 1 commit into
mainfrom
fix/binary-name-collision

Conversation

@charlesgreen

Copy link
Copy Markdown
Contributor

Charles installed v0.4.0 and ran aixgo version — and got v0.7.1 darwin/arm64, the Aixgo framework's CLI (github.com/aixgo-dev/aixgo/cmd/aixgo), which has owned the aixgo binary name since March. Both tools installed to the same GOBIN/aixgo, last install wins, silently.

The coding agent yields the name: cmd/aixgocmd/aixgo-code, and every CLI invocation in the code, workflows, templates, and docs gains the suffix (aixgo-code init, aixgo-code run, …). Unchanged on purpose: .github/aixgo.yml, the aixgo.yml workflow names, ax:* labels, the App handle, and all AIXGO_* variables/secrets — none of those collide with anything.

Prepared as v0.5.0 (one day after v0.4.0, before any external adopter exists — the cheapest moment this fix will ever have): changelog section written, all four pins bumped, ./scripts/verify-release.sh v0.5.0 passes, make check green.

The Aixgo framework's CLI is already installed as aixgo
(github.com/aixgo-dev/aixgo/cmd/aixgo, v0.7.x), so v0.4.0's binary
silently overwrote it in GOBIN, and installing the framework overwrote
the agent right back. The coding agent yields the name.

cmd/aixgo moves to cmd/aixgo-code and every documented invocation gains
the suffix. The config file, workflow names, labels, App handle, and
AIXGO_* variables are untouched. Pins and the changelog are prepared for
v0.5.0.
@charlesgreen
charlesgreen merged commit a581638 into main Aug 9, 2026
2 checks passed
@charlesgreen
charlesgreen deleted the fix/binary-name-collision branch August 9, 2026 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant