From the WASM decider roadmap (formerly WASM_TODO.md, now retired).
Distribution pipeline: PR merges, CI builds the component artifact, pushes it to a registry, and the platform service pulls it by digest.
Requirements:
- Digest pinning from the start
- Signing and provenance can come later
- Platform-side: pull-by-digest support in the wasm decider host service (which currently loads components from configured filesystem paths)
Why: components are only independently deployable from the host runtime once they are distributed as pinned artifacts instead of files baked into the repo checkout.
From the WASM decider roadmap (formerly WASM_TODO.md, now retired).
Distribution pipeline: PR merges, CI builds the component artifact, pushes it to a registry, and the platform service pulls it by digest.
Requirements:
Why: components are only independently deployable from the host runtime once they are distributed as pinned artifacts instead of files baked into the repo checkout.