Stable Public Trial

Historical record: the trial completed successfully and 0.1.0 was published on August 19, 2026. For current installations, follow Getting Started.

The stable-release gate required one complete 35-package release candidate to remain public for 14 consecutive days without a release-blocking defect.

The trial version was 0.1.0-rc.9. All 35 packages, including WASM, bindings, and platform sidecars, were published for the observation period. Registry closure and fresh-install verification completed at 2026-07-30 06:29 +08:00, which was the recorded T0. The earliest eligible instant was 2026-08-13 06:29 +08:00 because no P0/P1 reset the clock.

Reproduce the historical trial

Install the Node package in a real project:

pnpm add imagemin-rs@0.1.0-rc.9

Run the codecs your application uses. The default install intentionally does not include Sharp. If you need AVIF, test the second path explicitly:

pnpm add sharp@0.35.3

Browser or Worker users can test:

pnpm add @imagemin-rs/wasm@0.1.0-rc.9

Report the package manager and version, Node/browser version, OS/architecture, install command, codecs exercised, and whether Sharp was installed. Do not attach private images; use a minimal synthetic or redistributable fixture. Submit results with the structured RC feedback form. The form links each report to the public evidence ledger.

Select Pass only when the tested paths completed successfully. For a failure, first create a minimal issue with the RC defect form and provide its issue number in the feedback form so the release impact can be triaged.

External reports remain welcome, but their count and platform coverage do not block the stable release. The mandatory Release workflow independently covers all eight native targets, default installation without Sharp, AVIF after explicit sharp@0.35.3 installation, and browser WASM.

What blocked stable

A security issue, data loss/corruption, supported-platform installation failure, crash, incorrect codec result, mismatched package version, missing license/source material, or broken WASM deployment blocks stable. A fix for one of these issues requires a new RC and restarts the 14-day observation window.

Minor documentation and ergonomics issues are still welcome but normally do not reset the clock. The current dates and gate status are maintained in the Roadmap.

The stable Release workflow reads structured issues directly from GitHub and fails closed until the 14-day observation period, defect links, and absence of open P0/P1 issues all verify. A P0/P1 closed at or after the configured T0 also fails the gate until a new RC and T0 replace the canonical trial configuration.