Repository navigation
Lifecase 0.1.2: safe reports and a portable verifier
Lifecase 0.1.2 protects your report outputs and includes the optional verifier in each portable archive.
- Existing output paths, including executable and symlink paths, are rejected before scenarios run. Publication uses exclusive file creation, so report writes cannot truncate existing files.
- JSON and JUnit must use distinct, fresh names. For another run, choose a new report directory. A write error is exit 2; publication of two reports is not atomic.
- Every archive now contains both
lifecase-fixtureandlifecase(.exeon Windows). No Go or .NET runtime is needed for the packaged verifier. The separate CliWrap integration suite still requires .NET 8. - Native fixture behavior and protocol v1 are unchanged. Previous releases remain available.
Extract the matching archive, verify its .sha256 sidecar, and run on macOS/Linux:
./lifecase version
./lifecase run --fixture ./lifecase-fixture --scenario exit --scenario flood --json reports/first.json --junit reports/first.xmlExpect version 0.1.2, exit 0 and two passing scenarios. PowerShell uses .\lifecase.exe and .\lifecase-fixture.exe. Remove the scenario flags to run the full suite; Windows marks POSIX signal behavior unsupported/skipped.
These exact assets passed native fixture, Go/race/vet, .NET/CliWrap and extracted-archive checks on Linux x64, macOS arm64 and Windows x64, including a report-overwrite attempt that must leave the fixture unchanged. The evidence uses synthetic processes; it does not prove arbitrary application process-tree cleanup. Binaries are not claimed to be signed or notarized; follow your local execution policy.
Source: dfe21cbe60b397edecc3beeb4cc658e3097b95b5
Verification: https://github.com/rad1092/lifecase/actions/runs/38242668548