Skip to content

feat: PulseEngine pipeline rules + P3 toolchain bump#442

Merged
avrabe merged 5 commits intomainfrom
feat/pipeline-integration-p3
Apr 13, 2026
Merged

feat: PulseEngine pipeline rules + P3 toolchain bump#442
avrabe merged 5 commits intomainfrom
feat/pipeline-integration-p3

Conversation

@avrabe
Copy link
Copy Markdown
Contributor

@avrabe avrabe commented Apr 13, 2026

Summary

  • New pipeline rules: meld_fuse (component fusion) and synth_compile (WASM→ARM AOT) with MeldFusedInfo/SynthCompiledInfo providers
  • Loom optimizer fix: input argument was -i (wrong), now positional (correct); added attestation and passes attributes; propagates WasmComponentInfo
  • Version registries: Loom 0.3.0, WSC/Sigil 0.7.0, Meld 0.1.0 added to checksum registry
  • P3 toolchain bump: wasm-tools 1.246.2, wasmtime 43.0.1, wit-bindgen 0.55.0, wac 0.9.0, wkg 0.15.0, binaryen 129, nodejs 24.14.1
  • Security: wasmtime 43.0.1 patches 12 CVEs; nodejs 24.14.1 patches 8 CVEs

Test plan

  • bazel build //wasm:defs — Starlark loading validated
  • bazel build //examples/basic:hello_component — full Rust component build with new toolchain (wasmparser 0.246.2, wit-bindgen 0.55.0)
  • CI: BCR multi-platform tests (Ubuntu/macOS/Windows × Bazel 7/8)
  • CI: Compatibility tests, smoke tests, integration tests
  • CI: Security validation, hermiticity check

🤖 Generated with Claude Code

avrabe and others added 5 commits April 13, 2026 15:52
…in versions

Integrate the PulseEngine pipeline tools into rules_wasm_component:

Pipeline rules:
- Add meld_fuse rule for static WebAssembly component fusion
- Add synth_compile rule for WASM-to-ARM Cortex-M AOT compilation
- Add MeldFusedInfo and SynthCompiledInfo providers

Loom optimizer fixes and enhancements:
- Fix input argument bug: Loom CLI expects positional input, not -i flag
- Add attestation attribute for transformation provenance control
- Add passes attribute for selective optimization pass control
- Propagate WasmComponentInfo through optimization

Version updates:
- Loom: 0.1.0-rc1 → 0.3.0 (12-pass optimizer, fused-component passes)
- WSC/Sigil: 0.4.0 → 0.7.0 (native binaries, attestation chains, SLSA)
- Add Meld 0.1.0 to checksum registry (4 platforms)
- Update P3 minimums: wasm-tools 1.246.2, wasmtime 43.0.1,
  wit-bindgen 0.55.0, jco 1.17.6, binaryen 129

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Update standard toolchain to P3-capable versions, unifying
the standard and P3 build paths:

Core toolchain:
- wasm-tools: 1.244.0 → 1.246.2 (async task.return fixes, stream intrinsics)
- wasmtime: 39.0.1 → 43.0.1 (WASIp3 snapshot, 12 CVE security fixes)
- wit-bindgen: 0.49.0 → 0.55.0 (futures::Stream adapter for Rust)

Composition and packaging:
- wac: 0.8.1 → 0.9.0 (updated wasm-tools internals)
- wkg: 0.13.0 → 0.15.0 (maintenance, fill all platform checksums)

Optimization and runtime:
- binaryen: 128 → 129
- nodejs: 24.14.0 → 24.14.1 (8 CVE security fixes)

Registry cleanup: keep latest + previous per tool (policy).
Update compatibility matrix with 1.246.2 entry.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The binaryen module extension tag had a stale default version of 123,
which was removed from the checksum registry. BCR and external consumer
tests use the default, not the MODULE.bazel override.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
BCR tests and external consumers may still reference binaryen 123 via
cached configs or older MODULE.bazel files. Keep all three versions
(123, 128, 129) in the registry to avoid breaking existing users.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The nodejs 24.14.1 checksums in the registry were from SHASUMS256.txt
which lists tar.gz hashes, but the jco toolchain downloads tar.xz
archives (different compression = different hash). Revert to 24.14.0
which has verified tar.xz checksums. The 24.14.1 entry remains in the
registry for future correction.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@avrabe avrabe merged commit b0135ca into main Apr 13, 2026
28 checks passed
@avrabe avrabe deleted the feat/pipeline-integration-p3 branch April 13, 2026 23:58
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