Skip to content

Update: verify omni binary in CI - #6

Merged
hawkfry merged 1 commit into
mainfrom
feat/ci-cli-verification
Mar 15, 2026
Merged

hawkfry merged 1 commit into
mainfrom
feat/ci-cli-verification

Conversation

@hawkfry

@hawkfry hawkfry commented Mar 15, 2026

Copy link
Copy Markdown
Collaborator

Why are we changing this?

The existing CI only verified formatting, package builds, and tests. That can still miss breakage in the actual shipped CLI entrypoint. We want CI to prove that the omni binary itself builds and responds to basic commands on supported runner platforms.

What has changed?

  • Split the workflow into separate format, test, and build-cli jobs.
  • Added explicit contents: read permissions to keep the workflow minimal.
  • Added a build-cli matrix on ubuntu-latest and macos-latest.
  • Built the real binary with go build -o bin/omni ./cmd/omni.
  • Added smoke checks for ./bin/omni version, ./bin/omni --help, and ./bin/omni auth --help.

How to test it and expected results?

  1. Run go test ./....
    Expected: all tests pass.

  2. Run go build -o bin/omni ./cmd/omni.
    Expected: the binary is created successfully.

  3. Run ./bin/omni version.
    Expected: prints dev.

  4. Run ./bin/omni --help and ./bin/omni auth --help.
    Expected: both commands print help output successfully.

  5. Open the GitHub Actions run for this PR.
    Expected: format, test, and build-cli jobs all pass, with build-cli running on both Ubuntu and macOS.

Checklist:

  • My pull request represents one logical piece of work.
  • My commits are related to the pull request and look clean.
  • My code follows our coding conventions.
  • My code has appropriate tests and documentation.

@hawkfry
hawkfry merged commit bb13380 into main Mar 15, 2026
4 checks passed
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