qol-cicd

qol-cicd

Scope

All CI/CD lives in the monorepo under .github/workflows/ and .github/scripts/. There are no shared or reusable workflows in a separate repo; each workflow file is the source of truth for its own behavior.

Workflow inventory, by role

• ci.yml - lint + test on push/PR. Plans affected crates via .github/scripts/affected_crates.py, then runs fmt, clippy -D warnings, and tests on an ubuntu + macos matrix. Skips itself on version-bump commits.
• plugin-version.yml - versioning. Runs on push to main (or dispatch); computes a bump per release unit from conventional-commit history, commits chore(plugins): bump plugin versions, and pushes <id>-vX.Y.Z tags.
• release.yml - plugin releases. Fires on a <id>-vX.Y.Z tag; resolves the tag to a crate, derives the platform matrix from that plugin's plugin.toml platforms via .github/scripts/plugin_matrix.py, builds, and publishes assets.
• qol-tray-release.yml - host release. Fires on a qol-tray-vX.Y.Z tag.
• release-prune.yml - scheduled cleanup of old releases.

Release units and tagging rules live in the qol-tray-release-flow skill; read it before cutting any release.

Editing guidance

• The Python release scripts under .github/scripts/ have tests in .github/scripts/tests/; ci.yml runs them on every push, and any script change needs a matching test change.
• Pin third-party actions to a commit SHA (the existing workflows all do).
• Keep RUSTFLAGS/clippy at -D warnings parity with local checks; a workflow that is more lenient than the local gate hides breakage until release time.
• Platform coverage derives from plugin.toml platforms - never hardcode a runner list for plugin builds.
• Run release pruning sub-daily at a non-zero minute and keep manual dispatch available; weekly cleanup allows bursty versioning to accumulate stale releases for too long.

Local verification

ruby -e 'require "yaml"; YAML.load_file(".github/workflows/release.yml"); puts "ok"'
python3 -m unittest discover -s .github/scripts/tests -p 'test_*.py'