SDK Release Pipeline to PyPI

SDK Release Pipeline to PyPI A workflow diagram generated by Archify. 01 / Trigger 02 / Verify 03 / Gate 04 / Release Verify Idempotency check Build + publish Push to main · paths filter · Trigger › Verify · paths filter Push to main paths filter paths filter SDK Tests · uv run pytest · Verify › Verify · no network SDK Tests uv run pytest no network Parity Suite · vs SDK fuzz · Verify › Verify · differential Parity Suite vs SDK fuzz differential Version on PyPI? · pypi.org JSON · Gate › Idempotency check · skip if known Version on PyPI? pypi.org JSON skip if known Skip · nothing to do · Gate › Build + publish · notice only Skip nothing to do notice only uv build · wheel + sdist · Release › Build + publish · verified uv build wheel + sdist verified PyPI · OIDC publish · Release › Build + publish · OIDC, no token PyPI OIDC publish OIDC, no token attestations version is new already published must pass green Legend Agent logic Policy Tool action External system

Parity is the real gate

  • • The unit suite proves the SDK agrees with itself; the differential suite proves it agrees with the server.
  • • It runs in the backend environment because it imports the server evaluator, so both sides are fuzzed with identical inputs.

No secret is stored

  • • Publishing uses PyPI Trusted Publishing over OIDC, so the repository holds no API token.
  • • The job requests only id-token: write on top of contents: read, and it runs in a named environment that can require manual approval.