Skip to content

fix(ci): restore otf cli to releases - #963

Merged
leg100 merged 1 commit into
leg100:masterfrom
raspbeguy:fix/restore-otf-cli-release
Jun 27, 2026
Merged

fix(ci): restore otf cli to releases#963
leg100 merged 1 commit into
leg100:masterfrom
raspbeguy:fix/restore-otf-cli-release

Conversation

@raspbeguy

Copy link
Copy Markdown
Contributor

What

Restore the otf client CLI to the release pipeline.

  • Add the otf build + archive entries to .goreleaser.yml (darwin + linux, amd64 + arm64), producing the otf_<version>_<os>_<arch>.zip asset.
  • Add ./cmd/otf to the Makefile build target.

No Docker image — otf is a downloadable client, not a daemon.

Why

The otf CLI was accidentally dropped from releases in 64716f9 ("fix(ci): broke release process"). That commit migrated goreleaser to v2 and introduced otf-job, but instead of adding a new build entry it repurposed the existing otf build/archive slot:

-  - id: otf
+  - id: otf-job
-    main: ./cmd/otf
+    main: ./cmd/otf-job

As a result, GitHub releases no longer ship the otf binary, even though docs/docs/cli.md still instructs users to download it. There is no documented decision to retire the CLI — it was collateral damage during the otf-job rollout.

Verification

  • make build now emits otfd, otf-agent, otf-job, and otf.
  • .goreleaser.yml is valid YAML and mirrors the existing otf-job entry (please confirm goreleaser check passes in CI).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@leg100
leg100 merged commit ff8ea2c into leg100:master Jun 27, 2026
4 checks passed
@leg100

leg100 commented Jun 27, 2026

Copy link
Copy Markdown
Owner

Thank you @raspbeguy, merged.

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.

2 participants