[miguel-heygen]

What

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

Clips that start partway into a voice recording now keep their sound to the end, even when the WAV file misreports its own byte rate. Variable-bound media also renders at the right length and loudness.

Fixes

• Engine: A clip that starts partway into a WAV whose header gives the wrong byte rate now plays the right sound to its end, instead of going quiet early or staying silent (7ae1ae649, #7541).
• Share: When you reach the hourly limit on review versions, the message now explains that limit (8a15d9fee, #7539).
• Projects: A composition can only look up files inside its own project folder (5a88c9938, #7534).
• Capture: A wrong captioning region or model name is reported before captioning starts (bcc1437d7, #7533).
• Producer: A video or sound set through a variable now renders at its clip's length and loudness (789d28121, #7529).

Docs & Examples

• Variables: Say what can be a variable, including a video or sound per account (28d69d9a9, #7530).

Internal

• CLI: Give each test file its own home so renders never wait on another file's lock (2b86c49dc, #7526).

Why

Ships the lost-sound fix (#7541): a clip that starts partway into a WAV whose header misstates its byte rate went quiet early or played nothing. Also ships the variable-bound media fix, the project path confinement, the earlier captioning check and the share limit message.

Related work

Follows chore: release v0.9.32 (#7520).

How

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

Release gate

Engine, producer 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: pending

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.33.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, 5:45 AM

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

[heygengenesis]

Approve at e2225f08. Nothing blocks this.

• The branch is current main (7ae1ae64, #7541) plus one release commit. All seven commits since v0.9.32 appear in both notes files, with the correct SHA and PR links.
• Outside the two notes files, the diff only changes 20 "version" strings from 0.9.32 to 0.9.33. The changed-file set matches the v0.9.32 release (#7520) exactly.
• CI, Docs, regression, preview-regression, Windows render, Lambda arm64, PR captures and both player-perf runs pass on this head. CodeQL is still running, but this commit changes no code.
• The "fails without the fix" rule doesn't apply here. This is a release PR, and each fix (for example #7541) brought its own test.

Non-blocking nit: the changelog tag "Parsers,lint,producer,cli" is the generator turning #7534's multi-scope commit into one tag. Every earlier entry uses single title-case tags, so "Parsers" (or "Projects", matching the notes heading) would read better.

Also non-blocking: the body still says the full release gate is "pending". Add the link before merging.