Add CI to build pyodide package

[airen1986]

With the acceptance of PEP 783, package maintainers can now build and publish Pyodide-compatible wheels (pyemscripten platform) directly to PyPI. Submiting this PR to build python package in python-calamine repository, so pyodide packages can be uploaded to PyPI

Summary by CodeRabbit

• New Features
  • Added support for building and publishing Pyodide-compatible wheels.
  • Pyodide artifacts are now included in the release process, so they’re available before package publication and GitHub releases.

[coderabbitai]

Warning

Review limit reached

@dimastbk, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 41 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fc4ecc02-ce2d-4844-af31-ae8071260284

📥 Commits

Reviewing files that changed from the base of the PR and between b88ad9c and 3454bb0.

📒 Files selected for processing (1)

• .github/workflows/CI.yml

📝 Walkthrough

Walkthrough

Adds a build-pyodide CI job that builds Pyodide wheels via cibuildwheel and uploads them as an artifact, updates release and gh-release job dependencies to wait on it, and adds a [tool.cibuildwheel.pyodide] section in pyproject.toml configuring the build selector, test dependency, and test command.

Changes

Pyodide build integration

Layer / File(s)	Summary
Pyodide cibuildwheel configuration pyproject.toml	Adds [tool.cibuildwheel.pyodide] section specifying build pattern cp314-*, pytest test dependency, and test command.
Pyodide build job and release wiring .github/workflows/CI.yml	Adds build-pyodide job installing the wasm Rust target, using Python 3.14 and cibuildwheel with CIBW_PLATFORM=pyodide to build and upload wheels-pyodide; updates release and gh-release job dependencies to include build-pyodide.

Estimated code review effort: 2 (Simple) | ~10 minutes

Sequence Diagram(s)

sequenceDiagram
  participant CI as CI Workflow
  participant BuildPyodide as build-pyodide job
  participant Release as release job
  participant GHRelease as gh-release job

  CI->>BuildPyodide: run cibuildwheel (CIBW_PLATFORM=pyodide)
  BuildPyodide->>BuildPyodide: upload wheels-pyodide artifact
  BuildPyodide-->>Release: satisfy needs dependency
  BuildPyodide-->>GHRelease: satisfy needs dependency
  Release->>Release: publish to PyPI
  GHRelease->>GHRelease: create GitHub release

Loading

Poem

A rabbit hops through wasm mist so light,
Pyodide wheels now spun just right 🐇
Builds and tests, then off they fly,
Waiting jobs give a satisfied sigh.
Hop, hop, hooray — release in sight! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: adding CI to build a Pyodide package/wheel.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Pull request overview

Adds Pyodide wheel building to the repository’s CI so Pyodide-compatible (pyemscripten) wheels can be produced and included in release publishing.

Changes:

• Configure cibuildwheel for the Pyodide platform (CPython 3.14) in pyproject.toml.
• Add a dedicated build-pyodide GitHub Actions job that builds and uploads Pyodide wheels.
• Make release jobs depend on the new Pyodide build job so artifacts are included in tag releases.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
pyproject.toml	Adds Pyodide-specific cibuildwheel build/test configuration.
.github/workflows/CI.yml	Introduces a build-pyodide job and wires it into release dependencies/artifacts.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.