Auwai

Release

Auwai uses semantic versioning for the product, the skill scripts, the knowledge schema, the ledger schema, and the four plugin bundles.

One version source drives the release:

make version-check fails if the first three disagree.

Before a release

  1. Update VERSION and skills/auwai/scripts/version.py.
  2. Update extensions/plugin_common/capabilities.json if the feature contract changed.
  3. Run make plugins to regenerate the four bundles and the capability matrix.
  4. Run make release-check.
  5. Run the storage suite with disposable PostgreSQL, MySQL, and MariaDB URLs.
  6. Run the local v6 regression and record the gates in docs/70-benchmarks/results.md.
  7. Complete security sign-off.
  8. Update CHANGELOG.md with the version, date, and migration notes.
  9. Run make dist and make install-test on Python 3.10 and 3.13.
  10. Commit the release branch and merge it before tagging.

Build artifacts

python -m pip install build
make dist

The dist/ directory contains:

Verify the checksums:

cd dist && sha256sum -c SHA256SUMS

Clean install gate

make PY=python3.11 install-test

The target creates a fresh virtual environment, installs only the wheel, runs auwai --version, auwai doctor, indexes a fixture repository, builds a full-read plan, and starts a local knowledge service for a health check.

CI

The required matrix is:

The release job runs only for a v* tag and depends on every required job. It builds the same artifacts and creates the GitHub release. A failed gate publishes nothing.

Tag and publish

git tag -a v1.0.0 -m "Auwai 1.0.0"
git push origin v1.0.0

The tag workflow rebuilds the artifacts from the tagged commit. Do not upload a local build in place of the workflow output.

Migration notes

Rollback

Keep the previous wheel, plugin bundle, database backup, and checksum file. Do not downgrade a knowledge database in place. Restore the backup, install the previous wheel, and run --check before starting the service.