Problem
PR #96 updates the chart roadmap to say that v0.0.1 is released with “PyPI + Pyodide wheels.” The PyPI release is available, but the Pyodide wheel is not currently published as a downloadable release asset.
Current evidence:
- The v0.0.1 GitHub release has no assets.
- The v0.0.1 release workflow built and runtime-verified the Pyodide wheel, but the tag's workflow did not include the later
publish-pyodide job.
- PyPI does not accept the
pyodide_2025_0_wasm32 platform tag.
This makes the new wording in docs/engineering/chart-roadmap.md inaccurate and leaves users without a durable public URL from which to install the wheel.
Proposed resolution
Choose one:
- Publish the runtime-verified v0.0.1 Pyodide wheel as an asset on the v0.0.1 GitHub release; or
- Change the roadmap wording to: “v0.0.1 is released on PyPI; the Pyodide wheel is runtime-verified but not yet publicly distributed.”
The public installation documentation should use the same status wording and, once published, link directly to the wheel.
Acceptance criteria
- The roadmap and installation docs describe the actual distribution status consistently.
- If the wheel is considered released, the v0.0.1 release provides a durable downloadable asset and installation URL.
Related: #96
Problem
PR #96 updates the chart roadmap to say that
v0.0.1is released with “PyPI + Pyodide wheels.” The PyPI release is available, but the Pyodide wheel is not currently published as a downloadable release asset.Current evidence:
publish-pyodidejob.pyodide_2025_0_wasm32platform tag.This makes the new wording in
docs/engineering/chart-roadmap.mdinaccurate and leaves users without a durable public URL from which to install the wheel.Proposed resolution
Choose one:
The public installation documentation should use the same status wording and, once published, link directly to the wheel.
Acceptance criteria
Related: #96