Skip to content

lightdrift-libraw 1.0.0

Latest

Choose a tag to compare

@unique01082 unique01082 released this 15 Aug 06:51
· 2 commits to master since this release
7bae428

lightdrift-libraw 1.0.0

Summary

Version 1.0.0 promotes the verified RC.2 SDK contract to stable without
changing its JavaScript, TypeScript, native, or legacy compatibility surfaces.
It is the default release for new installations.

Install

npm install lightdrift-libraw

The default npm latest dist-tag resolves to 1.0.0. Existing applications can
pin lightdrift-libraw@1.0.0 for reproducible installs.

Stable contract

  • Typed Promise-based LibRaw API for ESM and CommonJS.
  • Complete safe camelCase mirror of LibRaw 0.22.2 with documented exclusions.
  • Per-instance FIFO native worker execution and cross-instance concurrency.
  • AbortSignal cancellation, structured LibRawError, copied input/output
    memory, idempotent close(), and reusable recycle().
  • Unified Sharp workflows for JPEG, PNG, TIFF, WebP, AVIF, and PPM.
  • Ordered bounded batch conversion and deterministic JPEG-setting heuristics.
  • Deprecated lightdrift-libraw/legacy compatibility throughout v1.

Compatibility

  • Node.js 22 and 24.
  • Linux glibc x64 and arm64.
  • macOS x64 and arm64.
  • Windows x64.
  • Vendored LibRaw 0.22.2 and zlib 1.3.2 source-build fallback.

Node.js 20, Alpine/musl, browser/WASM, system LibRaw, and incremental streaming
are outside the v1 support matrix.

Release verification

The stable tag is published only after the same protected workflow that
validated RC.2 passes again for 1.0.0:

  • Five platform/architecture prebuild jobs.
  • Linux vendored source-build fallback.
  • Full stable suite under ASan and UBSan, including malformed input handling.
  • Production dependency audit and package-content validation.
  • Clean packaged ESM and CommonJS consumers on Node.js 22 and 24.
  • npm trusted publishing with SLSA provenance and a CycloneDX SBOM.

Upgrade notes

Applications already using RC.2 require no code changes. Beta applications
should follow the migration guide or temporarily use the deprecated /legacy
entry point.

Related