[miguel-heygen]

What

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

Why

Ships a muted video's picture that no longer waits on its own audio track at a cut (#7412), and the seeded render: re-rendering a film with the same settings now gives the same result (#7410).

It also carries capture pages that load only the clips on screen (#7402), a check that replays an unchanged project's last pass and takes --no-craft (#7398), and a CI change that installs ffmpeg through the GitHub API asset route (#7401).

Related work

Follows v0.9.23 (#7399). Replaces #7411, closed unmerged, so v0.9.24 was never published and this release's notes and compare link run from v0.9.23. Refs #7412, #7410, #7402, #7398, #7401.

What I measured

• bun run release:prepare 0.9.25 --from <v0.9.23 commit> ran on current main (a remote Linux copy without tags): the first run drafted the notes, the summary is by hand with both notes markers removed, 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.23 release: the same count of 22 files, 15 package manifests, 5 plugin manifests and the docs changelog, plus releases/v0.9.25.md. The compare link is v0.9.23...v0.9.25. No package manifest is left at 0.9.23.
• bun run format:check exit 0.
• The release branch is one commit on main at fa2e635, with no tag at its head.

What I did NOT exercise

• CI on this PR, including the packed package size budgets, is still running.
• Desktop has not yet walked with this PR's packed packages (oss-release-gate); that run starts now.
• The published CLI: I will render with it once it is on npm.

No visible change

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

Small on purpose: a release bump, version lines only.

[mintlify]

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

Project	Status	Preview	Updated
hyperframes	🟢 Ready	View Preview	Nov 8, 2026, 7:25 PM

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

[heygengenesis]

Approving at e204da40.

• Commit range: v0.9.23...head is exactly #7401, #7402, #7398, #7410 and #7412 (fa2e63515) plus this release commit, and head sits directly on current main. #7411 closed unmerged, no v0.9.24 tag exists, and 0.9.24 isn't on npm (@hyperframes/core and @hyperframes/producer top out at 0.9.23). Notes running from v0.9.23 are therefore correct.
• Version bump: 20 manifests move from 0.9.23 to 0.9.25. No 0.9.24 remains anywhere, and no 0.9.23 remains outside the changelogs.
• Notes: releases/v0.9.25.md and the docs/changelog.mdx entry list the same bullets with the correct commits and PRs. The #7412 entry matches the change I reviewed and approved at e74ae6d2.
• CI: every workflow on this head is green, including Windows render verification, Player Safari perf and the Lambda image.

Not observed by me: the oss-release-gate desktop walk, which the body says is still running. It isn't a GitHub Actions run on this head.