Release Governor
Block promotion when malformed LLM outputs leak past staging validation boundaries.
Designed for staging/pre-prod environments with structured CI/CD workflows.
Install
pip install llm-release-governor
What it does
Release Governor sits between your CI contract checker and your staging environment. It consumes a locc artifact, detects leakage the contract checker allowed through, and enforces a promotion policy per environment.
locc (CI) -> Release Governor (staging gate) -> EGA (runtime)
Quickstart
release-governor evaluate \
--locc-artifact locc_result.json \
--env staging \
--sha $GIT_SHA
Exit 0 = ALLOW, Exit 1 = BLOCK, Exit 2 = REQUIRE_OVERRIDE
What it detects
| Type | Signal |
|---|---|
| PII leakage | PII signals in locc check reasons |
| Schema leakage | Structural diffs locc allowed through |
| Policy leakage | Promotion violates env-specific rules |
Override path
release-governor override create \
--env staging \
--approved-by alice \
--reason "confirmed false positive" \
--leakage-types pii \
--sha $GIT_SHA \
--identity-hash $ARTIFACT_HASH \
--expires-in-days 7
Then: commit the override file and re-run evaluate.
Audit log
release-governor evaluate \
--locc-artifact locc_result.json \
--env staging \
--sha $GIT_SHA \
--audit-log rg_audit.jsonl
{"event_type": "PROMOTION_BLOCKED", "sha": "...", "actor": "system"}
GitHub Actions
- name: Gate promotion
run: |
pip install locc llm-release-governor
locc run --contract contracts/current.json \
--snapshot snapshots/current.json \
--output json > locc_result.json
release-governor evaluate \
--locc-artifact locc_result.json \
--env staging \
--sha ${{ github.sha }}
Environment policies
| Environment | Policy |
|---|---|
| staging | FAIL blocks. HOLD allowed if no schema leakage |
| preprod | FAIL or HOLD blocks |
| prod | PASS only, no diffs, no leakage |
Stack integration
Release Governor is part of the LLM Reliability Stack.
Consumes locc artifacts. Sits upstream of EGA.
| Layer | Tool |
|---|---|
| Design-time | PFA |
| CI | locc |
| Staging | Release Governor |
| Runtime | EGA |
License
MIT
Publishing
Releases are published automatically to PyPI on version tag push.
To release:
git tag v0.1.0
git push origin v0.1.0
To dry-run on TestPyPI first:
Trigger the "Publish to TestPyPI" workflow manually from GitHub Actions.
PyPI trusted publishing must be configured once per project:
PyPI project settings -> Publishing -> Add publisher Owner: Repository: Workflow: publish.yml Environment: pypi
Metadata
Release files for llm-release-governor 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| llm_release_governor-0.1.0.tar.gz | 20.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| llm_release_governor-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.5 kB
Release files / llm_release_governor-0.1.0.tar.gz
| Download URL | llm_release_governor-0.1.0.tar.gz |
|---|---|
| Size | 20.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f01061328dcccb1e3b157f013c2b590559c65390f2406f80778c74db438d1622
|
|
BLAKE2b-256 checksum How to use checksums |
3c936da1830f6114f3eb4fbff3e02b9ff47c1f244279dabc3b14a5d65b76d647
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 7, 2026.
Transparency logRelease files / llm_release_governor-0.1.0-py3-none-any.whl
| Download URL | llm_release_governor-0.1.0-py3-none-any.whl |
|---|---|
| Size | 15.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1b86ef2805c250013dee596889d21dc7073e7867a412a7d6a2c72c07db5a9f2e
|
|
BLAKE2b-256 checksum How to use checksums |
88e3eeb1431c9a8894813083f4bc8893b4fb929c6ba51ff003b871b2252fd909
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 7, 2026.
Transparency log