v0.24.3 — no credential at all

Nothing new to install

Nothing that ships changed since v0.24.0. This closes out the release plumbing.

What it proves

Publishing now authenticates by trusted publishing: npm trades the short-lived token GitHub mints for this one workflow run for permission to publish. There is no long-lived credential in the repository to leak, rotate or forget — and the provenance attestation tying each tarball to this repository and build is generated automatically.

The path runs with nobody in it: publishing a release triggers a workflow that runs the tests, checks the tag against package.json, skips anything already on the registry, publishes, and confirms the registry has it.

Install is unchanged: curl -fsSL https://moshcoding.com/install.sh | sh, or npm i -g moshcode.