CI and releases

On every pull request

GitHub Actions runs ci.yml:

Job	Runner	What it checks
Lint	Ubuntu	`ruff check` on the Python, `shellcheck` on the installer
Python tests	macOS (Apple Silicon)	`pytest` with the locked dependencies, MLX included
JavaScript tests	Ubuntu	`node --test` on the browser modules
TypeScript core and Python parity	macOS (Apple Silicon)	Type-checks the shared core, compares it with Python and checks the native inference protocol
Published model parity	macOS (Apple Silicon)	Downloads pinned model files and checks them against reference fixtures
Browser storage	macOS (Apple Silicon)	Chromium and WebKit storage, audio decoding and model checks, plus synthetic-microphone and timestamped audio capture tests
Website	Ubuntu	`astro check` and a production build of `site/`

The model jobs cache their downloads by the pinned catalog; a newer push to the same pull-request branch cancels the run in progress. The Simulator and TestFlight checks are not implemented yet.

Vercel builds every pull request that touches site/ and comments with a preview URL. Merging to main deploys the site to production.

After merging

On every push to main, and weekly, the Installer job runs the one-line installer on a clean macOS runner, without downloading the models, and starts the installed command. This checks that a fresh install still works for new users.

Keeping dependencies fresh

Dependabot opens grouped monthly pull requests for Python (uv.lock), the website’s npm packages and the GitHub Actions versions. CodeQL scans the Python and JavaScript on every pull request.

Releasing

Update version in pyproject.toml and merge it.
Tag the merge commit and push the tag:
Terminal window
```
git tag v0.2.0
git push origin v0.2.0
```

The Release workflow checks that the tag matches pyproject.toml, runs the tests, and publishes a GitHub release with notes generated from the merged pull requests. Users get it with piano-duet update.