Repository navigation
Levenshtein v0.3.0
Levenshtein v0.3.0 improves verification correctness, native tool isolation, release packaging, and the path to adopting checks in GitHub Actions.
Highlights
- Add a minimal GitHub Actions starter workflow and clearer setup documentation.
- Add CLI
--versionand optional build, implementation, and native toolchain identity in reports. - Isolate native helper binaries by implementation and build identity, and prevent executable publication from leaking writer descriptors into forked children.
- Bound native subprocess output and reject malformed or incomplete diagnostics rather than accepting a clean prefix.
- Detect orphaned baseline entries and stale or ambiguous mutation acceptances.
- Add configuration version 2 with explicit community-rule completeness; version 1 remains supported.
- Include legal, contribution, security, and support metadata in release archives. Archives are built for Linux and macOS on amd64 and arm64, with SPDX SBOMs and SHA-256 checksums.
- Add contributor test tiers, a public roadmap, parser fuzzing, and reproducible synthetic native performance measurements.
Upgrading from v0.2.0
This minor release can expose findings or check errors that earlier versions missed. Review new baseline and mutation failures before accepting or deleting them, and investigate truncated or malformed tool output.
Configuration version 1 keeps its existing behavior. If you opt into version 2, selected native Go lint with participating community rule modules requires Dagger or an explicit lint.rule_modules=false opt-out. The opt-out skips those rules.
JSON report and baseline versions remain 1; strict report consumers should tolerate the new optional fields. The first run can rebuild tools and recompute affected cached results.
The native Go toolchain remains Go 1.27.1. Source-launcher bootstrap requires Go 1.21+; Dagger checks require a Docker-compatible runtime.
v0.3.0 ships Apache License 2.0 with NOTICE. Earlier published releases retain their original MIT license and contents. SDK security fixes preserve Dagger 0.21.9 compatibility; upgrading does not repair already downloaded historical archives.
See the full changelog and migration guidance, setup guide, and release archive instructions.
The root v0.3.0 tag and nested runner/lint/v0.3.0 tag identify the same release commit. The root GitHub Action is available at this release; a Marketplace listing is a separate owner publication step.