Repository navigation
Release v0.1.1
flatline 0.1.1
This release expands the public 0.1.x line with opt-in enriched decompiler output, broader supported runtime-host coverage, and a production-ready published-wheel workflow.
Added
- Opt-in enriched output via
DecompileRequest.include_enriched_outputandDecompileResult.enriched_output, exposing post-simplification pcode ops and varnode use-def graphs as frozen value types.
Changed
VersionInfonow exposesdecompiler_version(the Ghidra engine version) instead ofupstream_tagandupstream_commit.ghidra-sleighis no longer pinned to an exact version.- Compliance attribution now references the vendored decompiler source through the
third_party/ghidragit submodule instead of hardcoded tag and commit constants. DecompileResult.metadata["decompiler_version"]now always reflects the Ghidra decompiler engine version, not the flatline package version.- Manual TestPyPI dispatches now require a unique package version instead of silently skipping duplicate uploads.
- The supported runtime-host contract now includes macOS arm64 and Windows x86_64. Linux aarch64 and macOS x86_64 remain published-wheel targets pending dedicated equivalent-contract lanes.
- The Tier-1 wheel matrix is now validated end to end on TestPyPI ahead of the first production PyPI publish.
- Release readiness tooling and docs now audit the staged
0.1.1production path after collapsing the earlier0.1.1.dev1TestPyPI candidate, while keeping the GitHub-release-to-PyPI trigger explicit. - The public
0.1.xrelease-line policy now explicitly allows backward-compatible support expansion and opt-in capabilities to ship as documented patch releases while flatline remains pre-1.0.
Removed
UPSTREAM_TAGandUPSTREAM_COMMITconstants fromflatline._version.- The runtime pin-drift warning that compared
ghidra-sleighto a hardcoded baseline.
Full changelog: v0.1.0...v0.1.1