Skip to content

v19.0.0

Choose a tag to compare

@github-actions github-actions released this 27 Jul 09:54
f93f57f

v19.0.0

This is an intentional breaking release. The supported application boundary is RuntimeLane → generated Intent/Observer values → Observation/Reading streams → Receipt. Runtime is the sole root runtime value; the v18 graph-first API and intermediate v19 prototypes are not supported package entry points.

Required migration for retained v18 state

Stop every v18 writer and back up the repository before any v19 process opens it. Rehearse first, then promote once:

npm exec --package=@git-stunts/git-warp@19.0.0 -- git-warp-v18-to-v19 --repo /path/to/repository --graph events
npm exec --package=@git-stunts/git-warp@19.0.0 -- git-warp-v18-to-v19 --repo /path/to/repository --graph events --apply

The rehearsal is non-mutating and disposable; promotion uses a compare-and-swap ref transaction and preserves additive recovery refs. Keep those refs until application reads, writes, and backups are independently verified. See the v19 migration guide.

Performance witness

On the exact merged-main Node 22/Linux gate, the representative 16-property migrated-v18 scan was 31.1% faster cold, 32.1% faster warm, used 20.1–21.3% less operation CPU, and issued 46.6% fewer Git commands than v18.2.1. A separate 256 MiB logical Observer stream completed under a 64 MiB old-space cap with 35.2 MiB peak heap. These are bounded workload contracts, not universal speed claims.

The generated PR list below includes intermediate designs that were intentionally superseded before release. The supported final surface is defined by the v19 README, changelog, and migration guide.

Registry publish summary

  • npm: published
  • JSR: published

Dist-tag: latest
Version: 19.0.0

If one registry failed, re-run only that job from Actions.

What's Changed

Full Changelog: v18.2.1...v19.0.0