Repository navigation
v0.16.0 — Policy Preview & Simulation
GitWire v0.16.0 helps operators understand policy changes before automation acts.
This release adds a non-mutating policy preview workflow for validating .gitwire.yml, simulating proposed policy against historical decisions, comparing current vs proposed behavior, and generating deterministic guardrail recommendations.
Highlights
- Policy validation API
- Policy preview dashboard
- Historical event simulation
- Policy diff impact view
- Guardrail recommendations
- Non-mutating safety model: no config saves, no queue jobs, no GitHub writes
Why it matters
GitWire's operating model is Decide. Execute. Prove.
v0.16.0 adds a new preflight layer before execution:
Validate policy. Preview behavior. Simulate impact. Review guardrails. Then roll out safely.
Operators can now answer:
- Is this
.gitwire.ymlvalid? - Which pillars does it enable?
- Is dry-run protecting this rollout?
- Which settings are risky?
- How would this policy behave against recent repository history?
- What changes compared to the current repo policy?
- Would this policy act on more events?
- What guardrails should be added before rollout?
Included PRs
- #32 — Policy validation API
- #33 — Policy preview dashboard
- #34 — Historical event simulation
- #35 — Policy diff impact view
- #36 — Guardrail recommendations
- #37 — Documentation + release
New API endpoints
| Endpoint | Purpose |
|---|---|
POST /api/config/validate |
Validate policy YAML, return errors/warnings/risks |
POST /api/config/simulate |
Replay proposed policy against historical events |
POST /api/config/diff-impact |
Compare current vs proposed policy behavior |
POST /api/config/recommendations |
Generate deterministic guardrail recommendations |
Test status
- 36 suites
- 766 tests
- CI green:
syntax-check,rules-tests,web-tests - CodeQL green
- Protected-branch flow with admin enforcement
- Deploy workflow passing on self-hosted runner
Release line
v0.14.0-public-baseline → v0.14.1 → v0.15.0 → v0.16.0