Outcome Engineering Release Process

Outcome Engineering releases are tag-driven. Pushing a vX.Y.Z tag triggers the GitHub Actions publish pipeline, which runs tests, builds the package, publishes to PyPI through trusted publishing, and creates a GitHub Release.

Prepare the release so the tag pipeline succeeds on the first try.

Preconditions

Verify these before editing release files. If any fail, stop and tell the user.

1. Clean working tree: git status --short
2. On main: git branch --show-current
3. Up to date with remote: git fetch origin and compare main with origin/main

If the user has not specified a release type, ask whether this is: