v0.3.2
Highlights
First release of the engine to npm — npm install @bloomengine/engine works as of this version. Beyond the package itself, the release wires up GitHub Actions so future tag pushes auto-publish via OIDC trusted publishing.
Features
- On-disk SDF cache — per-mesh SDFs are now cached to disk, so cold restarts skip the bake step (closes #22).
- npm packaging —
@bloomengine/engineships TypeScript sources, the engine's Rust crates, and vendored JoltPhysics sources. A singleinstallis enough; no postinstall step. Tarball is ~2 MB packed / 8 MB unpacked. - Updated docs — README install instructions, scoped import paths (
from "@bloomengine/engine"everywhere), prereqs section covering Perry / Rust / wasm-pack.
Infrastructure
- Tag-driven release flow — pushing a
v*tag firesrelease.yml, which gates on theTestsworkflow, creates the GitHub Release, and publishes to npm. - OIDC trusted publishing — no long-lived
NPM_TOKENsecret, provenance attestation automatic. prepackguard — refuses to publish a tarball without an initialised JoltPhysics submodule, so the registry never gets a broken package.