Skip to content

chore: release v0.7.0#137

Merged
avrabe merged 1 commit into
mainfrom
release/v0.7.0
May 11, 2026
Merged

chore: release v0.7.0#137
avrabe merged 1 commit into
mainfrom
release/v0.7.0

Conversation

@avrabe
Copy link
Copy Markdown
Contributor

@avrabe avrabe commented May 11, 2026

Summary

Release v0.7.0. Single feature: DWARF Phase 1.5 (#135, lands sub-#130).

Behaviour change

Default FuserConfig.dwarf_handling flips from implicit
passthrough to explicit DwarfHandling::Strip. Callers that
previously relied on DWARF being passed through must opt in:

let config = FuserConfig {
    dwarf_handling: DwarfHandling::PassThrough,
    ..FuserConfig::default()
};

Rationale: the passthrough is wrong — addresses reference per-input
code-section offsets, not the merged code section. Downstream MC/DC
tooling (pulseengine/witness) was silently getting bad source
attribution. Phase 2 (#130) will add a real address-remap pass; until
then, Strip is the only non-corrupting setting.

Changelog

See CHANGELOG.md [0.7.0] for the full entry, including the new
Breaking section.

Safety

Test plan

  • CI green on smithy
  • After merge: tag v0.7.0, push tag, verify release.yml builds
    binaries for all four targets and creates the GitHub release.

🤖 Generated with Claude Code

DWARF Phase 1.5 (#135 / sub-#130): switch the default DWARF policy
from silent passthrough to explicit Strip. Passing input `.debug_*`
sections through verbatim produces wrong source-line attribution
against the merged code section — strictly worse than no DWARF for
downstream MC/DC tooling. `DwarfHandling::PassThrough` remains
available for callers that knowingly accept the lossy mapping.

This is a behaviour-changing default but the change is contained:
non-debug-info input is unaffected, and PassThrough preserves the
prior shape for any callers that need it. LS-CP-4 added.
@avrabe avrabe merged commit 59e76d8 into main May 11, 2026
10 of 18 checks passed
@avrabe avrabe deleted the release/v0.7.0 branch May 11, 2026 05:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant