Skip to content

v0.3.3 - Coverage Workflow Hardening

Choose a tag to compare

View all tags
@BartWaardenburg BartWaardenburg released this 13 Apr 08:54
· 339 commits to main since this release
v0.3.3
This tag was signed with the committer’s verified signature.
BartWaardenburg Bart Waardenburg
GPG key ID: 0F3DC0B8D9F6E258
Verified
Learn about vigilant mode.
37ad90f
This commit was signed with the committer’s verified signature.
BartWaardenburg Bart Waardenburg
GPG key ID: 0F3DC0B8D9F6E258
Verified
Learn about vigilant mode.

New crates / packages

  • No new crates or top-level packages in this patch release.
  • The existing npm wrapper packages now participate more reliably in the release and test flow.

Features

  • Added a first-class offset-based coverage helper for @srcmap/sourcemap-wasm.
  • Added a fallow-cloud-style coverage benchmark fixture that models cached maps and beacon-style offset batches.

Performance

  • Optimized coverage offset lookup paths for repeated batch workloads.
  • Added batch-oriented measurement for WASM and NAPI lookups so the benchmark reflects the real bulk coverage path instead of only individual lookup loops.

Bug fixes

  • Fixed release/version synchronization so newly published JS wrapper packages stay aligned.
  • Fixed CI and release workflow issues around npm publishing, benchmark imports, and JS hygiene.
  • Corrected coverage helper compatibility across WASM and NAPI batch APIs.

Breaking changes

  • None.

Infrastructure / CI

  • Expanded JS test coverage to include wrapper and compat suites.
  • Extended coverage/reporting to cover more of the published JS surface.
  • Tightened CI around benchmark compilation, JS hygiene, and production-coverage workflow validation.

Full Changelog: v0.3.2...v0.3.3

Assets 2
Loading