Files
zooqueenandHanzo Dev 70b41673a3 frames: rebrand the fork to Hanzo Frames
Forked from HyperFrames (Apache-2.0), full history preserved.

Hosts are mapped explicitly and BEFORE the identifier rename, because
hyperframes.heygen.com is not decoration: 175 of its occurrences are $schema
identifiers that a validator dereferences. A blind rename would have left them
naming a host that never serves them. The schema files are in this repo under
docs/schema, so the mapped host is one we can actually serve -- that is the
condition that makes the rewrite safe, and serving them is a deploy task, not
an edit. docs/schema/hyperframes.json is renamed to frames.json to match the
identifier it is now published under.

api.heygen.com and the CLI auth against heygen.com are left UNRENAMED on
purpose. They are a dependency on HeyGen's SaaS, not a name of ours to take,
and the right move is to remove that integration rather than rebrand it.

LICENSE and CREDITS.md are untouched; NOTICE records the lineage.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-28 23:42:24 -07:00

848 B

Frames v0.6.120

Released on 2026-06-21.

This hotfix restores Node-compatible package entrypoints for published Frames packages, so npm consumers load built JavaScript and declaration files instead of source TypeScript. It also improves page-side rendering so shader transitions paint correctly and final-scene content remains visible through the end of the render.

Fixes

  • Publish Node-compatible package entrypoints (2612b9bd, #1622)
  • Shader Transitions: Page-side render dropped shader transitions and final-scene content (a85a507c)

Full changelog

https://github.com/hanzoai/frames/compare/v0.6.119...v0.6.120