Skip to content

chore: May 2026 toolchain baseline + wasi-sdk-32 checksum fix#464

Merged
avrabe merged 2 commits into
mainfrom
upgrade/toolchain-versions-2026-05
May 20, 2026
Merged

chore: May 2026 toolchain baseline + wasi-sdk-32 checksum fix#464
avrabe merged 2 commits into
mainfrom
upgrade/toolchain-versions-2026-05

Conversation

@avrabe
Copy link
Copy Markdown
Contributor

@avrabe avrabe commented May 20, 2026

Summary

Realigns toolchain version pins with the checksum registry, and fixes a set
of stale checksums the version bump flushed out.

Version bumps (MODULE.bazel, toolchain .bzl files)

  • wasm-tools 1.244.0 → 1.246.2
  • wasi-sdk 29 → 32
  • binaryen 123 → 129 (TinyGo's internal _BINARYEN_VERSION + the
    binaryen_toolchain attr default — aligns with the standalone binaryen
    toolchain already registered at 129)
  • nodejs 24.14.0 → 24.14.1 (unifies the rules_nodejs host toolchain
    with the version jco already uses)
  • file-ops-component 0.1.0-rc.3 → 0.2.0

All target versions already had verified checksums in checksums/tools/*.json.

wasi-sdk-32 checksum fix

All five wasi-sdk-32 SHA256 checksums in checksums/tools/wasi-sdk.json
were stale — upstream re-released the v32.0 release assets after this repo
recorded them on 2026-03-15. Any wasi-sdk-32 build would have failed at
download. Re-verified by downloading all 5 platform tarballs from the
official GitHub release URLs and recomputing sha256.

Documentation & decision records

  • docs/certification-pipeline.md — the end-to-end pipeline
    (spar → build → loom/wasm-opt → wac → sigil → meld → witness/synth) with a
    mermaid flow diagram.
  • artifacts/decisions.yaml — rivet design-decision artifacts (DD-001..003)
    • driving requirements (REQ-002..004). rivet validate passes.

Validation

bazel build //examples/... builds 528/650 targets. The remaining
failures are pre-existing and unrelated: a ctx.toolchains.get() bug
(commit 6bbd9873, fixed separately) and python_component
(componentize-py is disabled by design). Before the wasi-sdk checksum fix
only 22/650 built — the fix is what unblocks the rest.

🤖 Generated with Claude Code

avrabe and others added 2 commits May 20, 2026 08:00
Version bumps (all target versions already had verified checksums):
- wasm-tools 1.244.0 -> 1.246.2
- wasi-sdk 29 -> 32
- binaryen 123 -> 129 (tinygo internal _BINARYEN_VERSION + binaryen_toolchain
  attr default; aligns with the standalone binaryen toolchain already at 129)
- nodejs 24.14.0 -> 24.14.1 (unifies the rules_nodejs host toolchain with the
  version jco already uses)
- file-ops-component 0.1.0-rc.3 -> 0.2.0

Fixes all 5 wasi-sdk-32 checksums in checksums/tools/wasi-sdk.json: upstream
re-released the v32.0 release assets after this repo recorded them on
2026-03-15, so every pinned sha256 was stale and any wasi-sdk-32 build would
fail at download. Re-verified by downloading all 5 platform tarballs from the
official GitHub release URLs and recomputing sha256.

Validated: `bazel build //examples/...` builds 528/650 targets. The remaining
failures are a pre-existing ctx.toolchains.get() bug (commit 6bbd987,
unrelated to this change) and python_component (componentize-py is disabled
by design).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- docs/certification-pipeline.md: the end-to-end pipeline
  (spar -> build -> loom/wasm-opt -> wac -> sigil -> meld -> witness/synth)
  with a mermaid flow diagram and per-stage tool table.
- artifacts/decisions.yaml: rivet artifacts capturing the decisions made
  while planning this work:
    REQ-002..REQ-004  driving requirements
    DD-001  Adopt the AADL-to-ELF certifiable WebAssembly pipeline
    DD-002  May 2026 toolchain version baseline
    DD-003  Integrate spar and witness now; defer synth pending a release

`rivet validate` passes (3 pre-existing unrelated warnings).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@avrabe avrabe merged commit 4b03422 into main May 20, 2026
35 of 36 checks passed
@avrabe avrabe deleted the upgrade/toolchain-versions-2026-05 branch May 20, 2026 19:31
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