The Intel sidecar and program died on their first import; two libssl copies were bundled under one name.
The DMG build now starts the sidecar once (openworker-server --check).
build_macos_cli.sh freezes the CLI, signs and notarizes it; the release attaches it for arm64 and x86_64.
install.sh downloads it on a Mac instead of the Python package.
Downloads the latest (or OPENWORKER_VERSION) tar.gz, checks its SHA-256, unpacks it into ~/.local/share and links ~/.local/bin/openworker.
macOS, musl and glibc older than 2.31 keep the uv/pipx route; the release publishes a stable-name checksum.
Linux x86_64 and aarch64 tar.gz from build_linux.sh, attached with versioned and stable names.
The macOS build installs the openshell extra (build_dmg.sh refuses to build without grpcio).
The test suite is broad (79 files) but has no coverage measurement or
threshold, so regressions in under-tested paths go unnoticed.
Add pytest-cov to dev dependencies, configure coverage in pyproject.toml
(branch coverage, source=coworker, show_missing), and update CI to run
pytest with --cov and upload the coverage.xml artifact.
The fail_under floor is set to 0 initially so CI passes without changes
to existing coverage. Once a baseline is established, the floor can be
ratcheted up over time.
Fixes#288
The GUI README tells contributors to run `npx tsc --noEmit` and `npm run build`
starts with `tsc`, but CI never runs either — a type error ships green today
and only surfaces when someone next builds a bundle locally. Add the check as
one step inside the existing gui-unit job so it reuses that job's npm ci and
costs no extra runner.
Verified locally: `npx tsc --noEmit` exits 0 on current main, and the vitest
suite (82 tests) still passes.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Release workflow adapted to the root layout (no monorepo paths, no .pth venv wiring).
New CI runs the coworker pytest suite and GUI unit tests; e2e joins once the inherited failures are fixed.
Rohit P