Repository navigation
Release Process
All 24 packages version in lockstep — one version number for the whole family (currently 1.0.1).
-
Changesets accumulate. Every change that should ship adds a
changeset (
.changeset/*.md) declaring patch/minor/major. The fixed group bumps all 24 packages together. - The Version PR opens itself. The Release workflow (changesets/action) keeps a "Version Packages" PR current — merging changesets updates it with version bumps and changelogs.
-
Merge the Version PR. That triggers the publish run:
turbo run build && changeset publish— all packages publish to npm with provenance attestations, and git tags@dusrel/<pkg>@<version>are created. - Verify like a user. The registry is checked per package (bulk publishes can take ~25 minutes to fully replicate — version documents appear before packuments do), and the consumer test is re-run against the published packages, in Node and in a real browser, before the release is called done.
- CI — lint, typecheck, unit tests, build, size budgets
- CodeQL analysis
- Browser tests — Chromium · Firefox · WebKit
- Docs build + Pages deploy
- WASM builds (when
native/**changed) — each with its in-Docker functional smoke gate
npm's OIDC trusted publishing cannot perform a package's first
publish, so the 1.0.0 bootstrap used a granular access token scoped
to @dusrel only, stored as a repo secret. The follow-up hardening —
migrating every package to trusted publishing and revoking the
token — is tracked in the repository's release notes and is the
standing next step (the token expires 2027-02-06, and npm retires
bypass-2FA direct publishing in January 2027).
| Version | Date | Notes |
|---|---|---|
| 1.0.1 | 2026-11-09 | Patch: setCodecAssets called after a codec's first use could return empty output (stale per-instance binding in the five Emscripten wrappers) — fixed in all 9 encode/decode sites, with browser regressions |
| 1.0.0 | 2026-11-08 | First release: all 24 packages — core engine, 10 WASM codecs, 9 feature packages, React/Vue/Svelte bindings, HEIC decode |
The full checklist lives in docs/RELEASE.md in the repository.
Released under the MIT License · © 2026 Dus Mamud · A Dusrel project · The HEIC engine (libheif/libde265) is LGPL-3.0, fenced to @dusrel/image-heic · Docs · Playground
Start here
Reference
Project
Elsewhere