three: v0.1.1

0.1.1 (2026-10-15)

Bug Fixes

• add package metadata and install usage across pixi, phaser and three (#27) (#28) (eee426c)

three: v0.1.0

0.1.0 (2026-10-15)

Features

• three: add native renderer and live ThreeRig (#25) (faa59b5), refs #23

pixi: v0.1.1

0.1.1 (2026-10-15)

Bug Fixes

• add package metadata and install usage across pixi, phaser and three (#27) (#28) (eee426c)

phaser: v0.1.1

0.1.1 (2026-10-15)

Bug Fixes

• add package metadata and install usage across pixi, phaser and three (#27) (#28) (eee426c)

phaser: v0.1.0

0.1.0 (2026-10-15)

Features

• phaser: add PhaserRig live player, shared page textures, and demo (#19) (#24) (13aab93)
• phaser: render meshes, clips and premultiplied pages (ae4bb3f)
• phaser: render region frames with native engine objects (#20) (098bdf0), closes #17

@rig-c/pixi 0.1.0

Initial GitHub release for the owner-published @rig-c/pixi@0.1.0 package.

The npm registry reports gitHead=d652ef6b8f4ee9098fdedc04be6cf2418c990fcf, six package files, and tarball SHA-1 3b174cfb7653f168c5ed8ffa4827978d685a700d. The downloaded registry tarball matches its SHA-1 and SHA-512 integrity.

The files are LICENSE, NOTICE, README.md, package.json, dist/index.js, and dist/index.d.ts. All six match the owner's existing local package at the published source: five byte-for-byte files and semantically equal package JSON. The isolated d652 worktree has the same tracked package files, with generated dist absent until build.

The owner performed the first npm publication locally with 2FA. This release records that already-published package; it performs no npm publish and makes no automated provenance claim.

Tag target: d652ef6b8f4ee9098fdedc04be6cf2418c990fcf. Release tag: pixi-v0.1.0. Open PR #13 proposes 0.2.0 only from the already-published workspace feature commit, so it is stale once this bootstrap is recorded.