Release
Operational reliability polish across CI, reports, and proof packs
A stability-focused release: cleaner report output, safer offline proof-pack flows, and CI/test hardening after the report rename.
Release: InvarLock 0.3.9 - Reliability and offline hardening
Highlights
- CI workflow test paths now match the report/certificate rename.
invarlock report explainnow prints the resolved drift band and keeps artifact path columns aligned.- Proof-pack tooling is more robust in offline and deterministic environments (including stdout config generation and packaging/import-safety test resilience).
0.3.9 is a practical cleanup release focused on reducing operational friction. Most changes are not flashy, but they make CI behavior, report readability, and proof-pack automation easier to trust when you are running repeatable evaluation workflows.
If you rely on offline runs or strict reproducibility, this release closes several small paper cuts that could otherwise create noisy failures or ambiguous output.
For more details, see CHANGELOG.md.
More from the blog
Continue through recent releases and implementation notes.
Release
Stable public contracts with stricter fail-closed verification
InvarLock 0.4.0 stabilizes contracts around policies, proof packs, and evaluation provenance while tightening verification, CI, and coverage enforcement.
Release
Coverage hardening across CLI, reporting, and observability paths
Coverage thresholds now enforce split-module branch floors for critical CLI/reporting paths.
Release
Targeted regression hardening for quantization and reporting paths
A focused hardening release: safer AWQ plugin discovery, stronger quantization clipping behavior, and broader report-schema acceptance for edge payloads.