[miguel-heygen]

What

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

Why

Ships the fix for exports failing on Windows: fast capture now works on Chrome 157 and newer, which wants content=drawable (#7626). It also carries every other change on main since v0.9.40: local renders keep Chrome's sandbox on where the host supports it (#7625) and launch Chrome with only the env it needs (#7629, #7630, #7634), publish leaves out outside files that came in with an imported project (#7598), cloud render --json listing the files an upload leaves out (#7631), the Studio timeline and overlays read an opaque preview over its channel (#7613, #7628), motion blur's compile hint and preview claim say what is measured (#7581), the blur trail mask test (#7624), and two CI and test housekeeping changes (#7627, #7536).

What people see

• Windows export: fast capture no longer fails at drawElementImage on Chrome 157+.
• Local render: Chrome's sandbox stays on where the host supports it.
• Cloud render: --json lists the files an upload leaves out.
• Publish: files outside the project that came in with an import are left out.
• Studio: the timeline and overlays read an opaque preview over its channel.
• Nothing else is new in this PR: it is the version bump and changelog.

No visible change

This PR is the version bump and changelog only. Each change above was captured in its own PR.

Test plan

• bun run release:prepare 0.9.41 ran on main at its current tip with all tags fetched; the notes list 13 entries from v0.9.40 and the compare link reads v0.9.40...v0.9.41.
• node scripts/ci/release-only-diff.mjs --verify passes on this commit ("release only: 22 files"), including the check that the notes link every commit since the last release.
• The branch is one commit on top of the main tip it was cut from, and no tag was pushed.
• CI on this PR, including the packed package size budgets.
• Desktop walked with this PR's packed packages in place of its pins.

[mintlify]

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

Project	Status	Preview	Updated
hyperframes	🟢 Ready	View Preview	Nov 13, 2026, 2:37 AM

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

[heygengenesis]

Verdict: REQUEST CHANGES · 1 blocker · 0 important · 0 nits — reviewed at 06fef6e2.

• blocker: main has moved past the commit this release was cut from (24d56e68). Two commits have landed since: 9701f4bbf (#7634) and 2591abfbf (#7631). Merging this PR would publish both to npm as v0.9.41, but releases/v0.9.41.md and docs/changelog.mdx don't list either one. The repo's own check catches this: release-only-diff.mjs --verify passes on the branch alone, but fails once the branch is merged into origin/main (releases/v0.9.41.md misses 2 commit(s) merged since the notes were drafted). Fix: rebase on main and rerun bun run release:prepare 0.9.41.

Scope

The 20 version bumps are all 0.9.40 → 0.9.41. The notes link all 11 commits in v0.9.40..24d56e68, and CI on this head is green. The packed-package Desktop walk in the test plan is still unchecked.