fix(ci): restore otf cli to releases - #963
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Owner
|
Thank you @raspbeguy, merged. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Restore the
otfclient CLI to the release pipeline.otfbuild + archive entries to.goreleaser.yml(darwin + linux, amd64 + arm64), producing theotf_<version>_<os>_<arch>.zipasset../cmd/otfto the Makefilebuildtarget.No Docker image —
otfis a downloadable client, not a daemon.Why
The
otfCLI was accidentally dropped from releases in 64716f9 ("fix(ci): broke release process"). That commit migrated goreleaser to v2 and introducedotf-job, but instead of adding a new build entry it repurposed the existingotfbuild/archive slot:As a result, GitHub releases no longer ship the
otfbinary, even thoughdocs/docs/cli.mdstill 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 buildnow emitsotfd,otf-agent,otf-job, andotf..goreleaser.ymlis valid YAML and mirrors the existingotf-jobentry (please confirmgoreleaser checkpasses in CI).