Add CI workflows for releasing Python and JavaScript packages

[jtmarks6]

Summary

This PR adds automated release workflows for publishing to PyPI and npm when a version tag is pushed.

What's included

• .github/workflows/release-python.yml - Builds manylinux wheels for:

  • Linux x86_64 (manylinux) - compatible with AWS Lambda, Docker, etc.
  • Linux aarch64 (ARM)
  • Windows x86_64
  • macOS
  • Source distribution

• .github/workflows/release-js.yml - Builds WASM and publishes to npm

• RELEASING.md - Documentation for the release process

Why this is needed

Currently only source distributions are published to PyPI. This means users on Linux (AWS Lambda, Docker, CI systems) must have Rust installed to compile subtr-actor-py. Pre-built manylinux wheels eliminate this requirement and make installation much faster.

Setup required (one-time)

Before the workflows will work, you'll need to configure secrets:

1. PyPI (choose one):

   • Trusted Publishing (recommended): Go to PyPI → Account Settings → Publishing → Add pending publisher with repo rlrml/subtr-actor, workflow release-python.yml, environment pypi
   • API Token: Add PYPI_TOKEN as a GitHub secret

2. npm: Add NPM_TOKEN as a GitHub secret

How to release (after setup)

# 1. Bump versions
just bump 0.1.11   # or manually edit Cargo.toml, python/pyproject.toml, js/package.json

# 2. Commit and tag
git commit -am "Release v0.1.11"
git tag v0.1.11
git push origin master --tags

The workflows trigger automatically on v* tags.

---

🤖 Generated with Claude Code

[colonelpanic8]

but wont this not work in ci because we havent set up the tokens in the github context?

[jtmarks6]

Yeah I haven't worked with github ci before, I usually use circleCI. I assumed there was a way to input tokens as secrets

[colonelpanic8]

there is, but i would need to generate them right, since i own the packages?

[jtmarks6]

Yes I think you would need to since you own it. Once it get setup it should publish to all the envs automatically and not need to be touched again