[miguel-heygen]

What

Release v0.9.42: the version bump for every package, the changelog entry and releases/v0.9.42.md. It carries 10 changes since v0.9.41, among them the Studio file-lock fix (a file held open or read-only now answers 423 or 403 with a reason) and the font step that parses a page once.

No visible change

This PR only bumps versions and adds release notes. Each change in it was captured in its own PR.

Test plan

• bun run release:prepare 0.9.42 ran clean from v0.9.41 (the changelog TODO and style-bar markers are gone from releases/v0.9.42.md and docs/changelog.mdx)
• CI Build green, then the release gate walks the packed packages before merge

[mintlify]

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

Project	Status	Preview	Updated
hyperframes	🟢 Ready	View Preview	Nov 13, 2026, 5:30 PM

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

[heygengenesis]

Requesting changes at e1f98bfa.

Blocker: CI Release checks fails at this head (run 43466689676):

releases/v0.9.42.md misses 1 commit(s) merged since the notes were drafted: 2c2b399 fix(producer): local renders bring in only media, font, CSS and JS from outside the project (#7647).

Main has moved one commit past this branch's base. If this merges as-is, v0.9.42 ships #7647 (a producer change to which outside files local renders load) without a line in releases/v0.9.42.md or docs/changelog.mdx. To fix it, rebase on main and rerun bun run release:prepare 0.9.42, or add a Fixes entry for #7647 to both files. Then CI and the release gate need to run again on the new head.

Everything else checks out:

• v0.9.41...e1f98bfa has exactly 7 commits, and each one is linked once in the right section of both note files, with SHAs and PR numbers matching.
• All 20 published manifests move from 0.9.41 to 0.9.42. The ones left unchanged (root, sdk-playground, studio/frontend, registry and runtime-lock sources) are private or vendored, not released.
• Every other workflow on this head passes (Windows render verification, regression, preview-regression, CodeQL, Docs, Lambda image, player perf).

Not a fix PR, so the "fails without the fix" requirement doesn't apply.

[heygengenesis]

Requesting changes at d2621adc.

This head fixes the earlier gap: #7647 and #7641 are now linked. But Release checks fails again (job):

releases/v0.9.42.md misses 1 commit(s) merged since the notes were drafted: 87c4a07 feat(studio): drag and resize draw live on an opaque preview over its channel (#7646).

This wasn't a race. #7646 landed on main at 17:01Z, and the release commit is from 17:22Z, so the rebase used a main that was already out of date. If this merges as-is, v0.9.42 ships #7646 with no entry in the notes. To fix it, fetch main, rebase, and rerun bun run release:prepare 0.9.42, or add #7646 under Features in both releases/v0.9.42.md and docs/changelog.mdx.

Verified at this head:

• v0.9.41...d2621adc has 9 commits, and each is linked once in both note files, with SHAs and PR numbers matching.
• All 20 published manifests move from 0.9.41 to 0.9.42.

[heygengenesis]

Approving at ad96a353.

• The missing-commit blocker is resolved. The branch is current main plus the release commit, with nothing new on main since. v0.9.41...ad96a353 has 10 commits, and each is linked once in both releases/v0.9.42.md and docs/changelog.mdx, with SHAs and PR numbers matching (including #7647, #7641 and #7646).
• All 20 published manifests move from 0.9.41 to 0.9.42. The packages left unchanged are private or vendored.
• CI is green on this head (run 43473010041), including Release checks. Windows render verification, regression, preview-regression, CodeQL, Docs, Lambda image and player perf also pass. The one cancelled CI run was replaced by the green run.

Not a fix PR, so the "fails without the fix" requirement doesn't apply. No blockers.