chore(release): v0.7.0 — f64 codegen + signing-e2e in CI#142
Merged
Conversation
Bumps workspace version to 0.7.0 and promotes the [Unreleased] entries (f64 ARM VFP-D codegen from #141, signing-e2e workflow from #140) to a v0.7.0 heading. Adds a falsification statement to the v0.7.0 notes per PulseEngine methodology: the release is wrong if (a) a covered f64 op miscompiles or fails to link on Cortex-M7DP, or (b) signing-e2e goes red on a clean v0.7.0 checkout. Case 3 (tamper-negative) is xfail until sigil#135 ships a fix; cases 1 and 2 must stay hard green. PRs included: #140 test(signing): wsc e2e in CI — pinned v0.9.0, sha256-verified #141 feat(backend): f64 codegen on Cortex-M7DP (non-optimized path)
3 tasks
avrabe
added a commit
that referenced
this pull request
May 25, 2026
The Cargo.toml workspace-package version was bumped to 0.7.0 in PR #142, but the per-crate `version = "0.6.0"` pins on path dependencies (introduced in #136 to give `cargo publish` real crates.io coordinates to rewrite to) were not swept. Cargo refuses to resolve `synth-backend = "^0.6.0"` against the local 0.7.0 path-dep, breaking both release.yml and publish-to-crates-io.yml on the v0.7.0 tag. This commit sweeps all 23 intra-workspace `version = "0.6.0"` pins (across 8 crate manifests) to `"0.7.0"`, and bumps the MODULE.bazel `module(version = ...)` declaration to match. The v0.7.0 tag was deleted from origin (no GitHub Release was produced — release.yml's build matrix failed before the 'Create GitHub Release' job, which was skipped) and will be re-pushed against this commit. Local validation: cargo metadata --no-deps # resolves at 0.7.0 cargo build --release -p synth-cli # green Follow-up tracked separately: docs/release-process.md should gain an explicit 'sweep intra-workspace pins' step (or a CI gate that fails when workspace version diverges from path-dep pins) so v0.8.0 doesn't repeat this.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
[Unreleased]entries to[0.7.0] - 2026-05-25Theme
Floating-point breadth + verifiable signing CI.
signing-e2e.ymlworkflow runs three wsc keyless cases against a sha256-pinned wsc v0.9.0 on every CI. Case 3 (tamper-negative) was demoted to xfail in7f1a9c9after discovering sigil#135 —wsc verify --keylessaccepts WASM modules whose signed payload has been byte-modified. Cases 1 + 2 remain hard checks.Falsification statement
v0.7.0 is wrong if any of:
CHANGELOG.md#0.7.0produces an ELF that fails to linki.MX RT1062orSTM32H743class)signing-e2e.ymlgoes red on a cleanv0.7.0checkout (cases 1 + 2 — case 3 is xfail until sigil#135 ships)Test plan
v0.7.0, watch release.yml ship the 10-asset GitHub Release (9 from feat(release): crates.io trusted publishing + toolchain SBOM (Phases 4+6) #136 + the toolchain SBOM)publish-to-crates-io.ymlrepublishes the workspace at 0.7.0 viaCARGO_REGISTRY_TOKEN