Back to blog

Report rename cleanup and offline evidence-pack hardening

A stability-focused release: cleaner report output, safer offline evidence-pack flows, and CI/test hardening after the report rename.

2 min readInvarLock Team
An indexed assembly is fully contained within its own boundaries, expressing a complete offline evidence surface.

Release: InvarLock 0.3.9 - CI cleanup, report readability, and offline package safety

Highlights

  • CI workflow test paths now match the report/certificate rename.
  • invarlock report explain now prints the resolved drift band and keeps artifact path columns aligned.
  • Evidence-pack, observability, packaging, and import-safety paths are more robust offline.

0.3.9 is a practical cleanup release after the report rename. CI workflow tests now follow the new report/certificate paths, and invarlock report explain prints the resolved drift band instead of a hard-coded threshold. The ARTIFACTS block is aligned so report output is easier to scan.

The rest of the release closes operational paper cuts that can make repeatable workflows noisy. CPU health checks no longer fail when platform CPU counts are unavailable, evidence-pack config generation can write to stdout without /dev/stdout, the memory-management integration test gets a PyTorch warm-up, wheel packaging can run with build --no-isolation, and import-safety tests skip cleanly when the network is unavailable.

The README branding updates in this release are cosmetic, but they support the same goal: make the public surface clearer while the evaluation/report terminology settles.

Sources

Website documentation explains the maintained workflow. The changes described here belong to InvarLock v0.3.9; the tagged release record preserves that historical scope.

More in Release

Explore nearby related posts.