rossoctl / rossoctl/cortex

test: release smoke test on macOS CI runners

Open
#956 0 comments 0 reactions 1 assignee View on GitHub

@Alan-Cha is already working on this.

Since Sep 10, 2026.

high priority
Dominant language
Go
Stars
13
Forks
40
Avg merge
12h 17m
Merged PRs (30d)
156

Description

Feature Description

The v0.9.0 exit bar says install works cold on four targets. Nothing checks that today, so every
release risks shipping an installer that only worked on the author's laptop.

Proposed Solution
  • CI job on macOS runners installing from a published tag exactly as a user would
    (curl | sh), not from a local build
  • Assert the launchd service starts and abctl service status is healthy
  • Drive a real request through the proxy and assert a parsed event with a non-zero token
    count, read through the unattended capture path (#955)
  • Assert upgrade-over-existing and uninstall-is-clean
  • Runs on every tag; a failure blocks the release
  • Also runs against main-latest, so breakage is caught before tagging
  • State which architectures CI covers and which stay manual
Additional Context

Part of the Cortex v0.9.0 release. Automates the macOS install verification (#944) and gates
exit criterion 1.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.