[miguel-heygen]

What

Release v0.9.34: version bump for 15 packages and 5 plugin manifests, plus the release notes for the ten changes since v0.9.33.

HyperFrames now runs helper programs like FFmpeg only from where they are installed, never from a project folder. Renders can also refuse variables a page does not declare, when that check is turned on.

Features

• Producer: With strict variables turned on, a render fails when it is given a variable the page does not declare. It is off by default, so renders are unchanged (f312fca7e, #7548).

Fixes

• Studio Server: Load fonts and modules only in the Studio's own preview frames (ffb13c3b6, #7553).
• Skills: Plugin launcher and media helpers run the pinned CLI, not a project copy (a8fe3a5b6, #7552).
• CLI: Preview uses the bundled Studio unless local Studio mode is opted in (668983e1a, #7551).
• Security: FFmpeg, FFprobe and other helper programs are taken only from where they are installed or a path you set, never from a project folder (84799bdc5, #7524).
• Core: Saving a file works on drives that refuse hard links with a permission error (f36463e29, #7474).
• Studio: Thumbnails are captured in a sealed page, and shader transitions still work where the browser blocks local storage (80cda85d7, #7528).

Catalog

• CLI: Refuse more coding-agent instruction files in registry installs (9bab57ab4, #7549).
• CLI and Studio: Registry installs and Studio file writes stay inside the project content folders (b96c82b78, #7523).

Internal

• Engine: The URL-read concurrency test passes on machines with 32 or more cores (3ad7611f9, #7544).

Why

Ships strict variables (#7548), off by default, so the renderer can turn the check on once a published engine carries it. Also ships the helper-program lookup fix (#7524), the Studio isolation fixes (#7528, #7553, #7523), the link() permission fallback (#7474) and the CLI and skills fixes.

Related work

Follows chore: release v0.9.33 (#7543).

How

bun run changelog:draft 0.9.34 --write --from v0.9.33, then the TODO summary was written and the style-bar line removed in both notes files, and five lines were put in plain words. Then bun run release:prepare 0.9.34 --from v0.9.33 --no-tag set 15 packages and 5 plugin manifests to 0.9.34. The changed file list matches the v0.9.33 release commit (22 files). No tag is pushed; the release workflow tags the merge SHA.

Release gate

Engine, producer, parsers and CLI code changed, so the full release gate runs on this head (Desktop's full walk with these packed packages). Link below when it finishes.

• Full gate on this head: PASS in 15 min, Desktop's full walk with the packed 0.9.34 packages

No visible change

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

Test plan

• Unit tests added/updated (release commit only, no code)
• Manual testing performed: diff checked to be only version strings plus the two notes files
• Documentation updated: docs/changelog.mdx and releases/v0.9.34.md, summary written by hand
• Comments follow CONTRIBUTING.md "Comments"

[mintlify]

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

Project	Status	Preview	Updated
hyperframes	🟢 Ready	View Preview	Nov 11, 2026, 4:01 PM

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

[heygengenesis]

Approving at 4b95111c. No blockers.

• Scope. Every changed JSON file differs from main only in its "version" line. That covers 15 packages and 5 plugin manifests. The only other files are docs/changelog.mdx and releases/v0.9.34.md. The file list matches the v0.9.33 release commit file for file, apart from the notes file's name. No public package is left at 0.9.33, and internal dependencies stay workspace:*.
• Notes. v0.9.33..merge-base is exactly the ten commits listed, and each SHA and PR link matches. The strict-variables entry correctly says the check is off by default.
• CI at this head. CI, regression, Windows render and PR captures all pass. One earlier PR-captures run was cancelled, and a later run passed.

Non-blocking:

• #7554, the comment-only fix, landed on main after this branch was cut, so it isn't in the notes. That's fine, since it has no user-facing effect.
• The "Full gate on this head: PASS" line has no link, although the section says one would be added. Adding the run URL would make the claim checkable from the PR.