[miguel-heygen]

What

Release v0.9.23: version bump, releases/v0.9.23.md, and the docs changelog. Merging publishes to npm.

Why

Ships the fade-in fix: a set written before the tween it sits inside no longer erases that tween's end in a render or in preview (#7397). Films built that way showed their cards vanish from the moment the fade ended on 0.9.19 to 0.9.22.

It also carries a failed CDN script's report that names its library and version (#7394), a menu row's highlight that is rounder than its panel (#7395), bounded Studio recovery with full-quality playback verified (#7393), preview health that names the media element that held play (#7159), and a test fix (#7119).

Related work

Follows v0.9.22 (#7392). Refs #7397, #7395, #7394, #7393, #7159, #7119.

What I measured

• bun run release:prepare 0.9.23 --from <v0.9.22 commit> ran on current main (a remote Linux copy without tags): the first run drafted the notes, the summary sentence is by hand, and the second run wrote the version bump with --no-tag, so no commit or tag was made by the script.
• The changed files match the v0.9.22 release commit: the same 15 package manifests, 5 plugin manifests and the docs changelog, plus releases/v0.9.23.md. Every versioned manifest reads 0.9.23. The compare link is v0.9.22...v0.9.23.
• bun run format:check exit 0.

What I did NOT exercise

• CI on this PR, including the packed package size budgets, is still running.
• Desktop has not walked with this PR's packed packages (oss-release-gate).

No visible change

Version bump and changelog only. Each change was captured in its own PR.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
hyperframes	🟢 Ready	View Preview	Nov 8, 2026, 6:32 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

[heygengenesis]

Approve at 513159ff. I found no blockers.

• Release range: the base is 75fe18c62 (#7397, the fade-in fix), which is the current tip of main. v0.9.22...base has exactly 6 commits (#7159, #7393, #7394, #7395, #7119, #7397). All 6 appear in the notes with matching SHAs, and none are missing.
• Manifests: the 22 changed files are the same set as the v0.9.22 release commit, with releases/v0.9.23.md in place of the v0.9.22 notes. All 20 versioned manifests move from 0.9.22 to 0.9.23. The manifests not bumped (root, sdk-playground, studio/frontend) are private and were also left alone in v0.9.22.
• Notes: releases/v0.9.23.md and the docs/changelog.mdx entry match, and the compare link is v0.9.22...v0.9.23.
• CI on this head: all workflows passed (CI, Docs, CodeQL, regression, preview-regression, Windows render, Player perf/Safari, Lambda arm64, PR captures).
• "fails without the fix" rule: it doesn't apply here. This is a release PR with no fix code. The fade-in fix and its test landed in #7397.

Not checked here: the desktop oss-release-gate walk with the packed packages, as the PR body says.