07 Workflow
SDK Release Pipeline to PyPI
What has to be true before a version of the SDK can reach PyPI, and why the parity suite is the real gate.
The unit suite proves the SDK agrees with itself. The differential parity suite proves it agrees with the server, by fuzzing both evaluators with identical inputs and requiring identical values, reasons, and rule ids. It runs again inside the publish workflow, so a package that breaks parity cannot be published.
What to look for
- The gate lane is the idempotency check: an already-published version is skipped, not failed.
- Publishing uses PyPI Trusted Publishing over OIDC, so the repository stores no API token.
- A merge that does not bump the version cannot break main.