[miguel-heygen]

What

Release v0.9.29: a version bump of all packages and plugin manifests, the changelog entry and releases/v0.9.29.md.

It carries six changes since v0.9.28 and nothing else:

• feat(cli): label GPT image prices as estimates and show the charged credits #7351: the CLI labels GPT image prices as estimates and shows the credits actually charged.
• fix(studio-server): history waits out a file a save has emptied, and rereads one written mid-copy #7480: Studio history waits out a file that a save has emptied, and rereads one written mid-copy, so undo no longer loses work.
• fix(producer): refuse a too-slow render only when its typical frame says it cannot finish #7479: a render is refused as too slow only when its typical frame says it cannot finish.
• fix(engine): a video clip shows a new source frame on every frame it is on screen #7471: a video clip shows a new source frame on every frame it is on screen.
• test(engine): split the frame extractor tests so each file stays under the flake gate budget #7476: test-only split of the frame extractor tests.
• docs(studio-app): the Reference read is paid by Pro or a saved HeyGen API key #7440 is a docs change (who pays for the Reference read).

Why

Ships the undo fix, the slow-render estimate fix, the per-frame video fix and the CLI's image price labels to npm, so apps that pin the CLI and Studio can take them.

Related work

Follows chore: release v0.9.28 (#7475).

How

bun run release:prepare 0.9.29 on release/v0.9.29 at main; the generated TODO summary was rewritten by hand in both notes files, then the command was rerun to cut the version. The changed file list matches the v0.9.28 release commit. No tag is pushed; the release workflow tags the merge SHA.

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.29.md, summary rewritten 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 10, 2026, 8:18 AM

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

[heygengenesis]

Requesting changes at 58baea1c. The release is stale against main.

What checks out: the diff is only version strings in the same 20 manifests as v0.9.28 (#7475), plus docs/changelog.mdx and releases/v0.9.29.md. No 0.9.28 string is left anywhere at head. v0.9.28...58baea1c is exactly #7471, #7440, #7476, #7479, #7480 and the release commit. Every Actions run on this head is green.

Blocker: #7351 (feat(cli): label GPT image prices as estimates and show the charged credits) merged to main at 08:00Z. That is six minutes after this PR opened, and it is not in this branch. The release workflow tags the merge SHA, so merging this as it stands would:

• ship #7351's CLI change (packages/cli/src/heygen/{generate,pricing,v3}.ts, media-use skill) to npm as v0.9.29;
• leave it out of the changelog entry, releases/v0.9.29.md and the PR's "five changes and nothing else" claim, while the compare/v0.9.28...v0.9.29 link would still list it;
• mean the Desktop walk PASS covers packed packages built without #7351, not the code being tagged.

Fix: rebase release/v0.9.29 on current main and rerun bun run release:prepare 0.9.29. Add #7351 under Features (CLI) in both notes files, update the PR body, then rerun CI and the Desktop walk on the new head.

The "fails without the fix" rule doesn't apply here: this is a release PR, not a fix PR.

[heygengenesis]

Approving at 05c527e7. The change request is resolved.

• The branch is re-cut on current main: 1 commit ahead, 0 behind. v0.9.28...05c527e7 is #7471, #7440, #7476, #7479, #7480, #7351 and the release commit.
• #7351 is under Features (CLI) in both docs/changelog.mdx and releases/v0.9.29.md. The tags and summary were updated to match.
• The diff is the same 22 files as v0.9.28: version strings only, plus the two notes files. No 0.9.28 string is left in any JSON at head. skills-manifest.json, which #7351 touched, has no version field.
• Every Actions run on this head is green.

The Desktop walk PASS on this head's packed packages is still the merge gate.