chore: release v0.8.45

[miga-heygen]

Important

On hold, do not merge as it stands. This release carries only the engine capability, which no render configuration can switch on, so publishing it would mean publishing again within the hour. It will be regenerated to carry #4020 as well, with one note saying the blur is opt-in and how to turn it on, replacing the paragraph below that says no configuration can reach it. Review is still welcome; the merge is what is held.

Publishes the single change merged to main since v0.8.44 (2026-09-17):

• feat(engine): sub-frame multi-sample motion blur #4019 Engine sub-frame multi-sample motion blur. For each output frame the capture path seeks the timeline to several sub-frame times across the shutter window, captures each, and averages them. Because it re-renders at every sample rather than offsetting copies of an element, it integrates rotation, scale, opacity, filters and child animation, which the motion-blur catalog component cannot do. Defaults follow After Effects: 16 samples, a 180 degree shutter at phase -90, averaged in sRGB with linear light as an opt-in. Composes with static-frame dedup, so only moving frames pay for the extra samples.

Read the notes before expecting to use it. This release ships the engine capability behind CaptureOptions.motionBlur, and no render configuration sets that option yet, so there is no flag that turns the blur on. The release notes say so explicitly rather than letting a reader hunt for one. Wiring it through the producer is #4020.

This PR changes only package and plugin versions, the changelog, and release notes. No source files change. Version bump produced by bun run set-version 0.8.45 --no-tag; the file set matches the v0.8.44 release PR (#4016) exactly (18 files), no 0.8.44 remains in any package.json or plugin.json, and the lockfile is untouched.

Compare: v0.8.44...release/v0.8.45

Merging this PR publishes: the workflow creates the v0.8.45 tag, publishes npm, and cuts the GitHub release.

Miga

[mintlify]

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

Project	Status	Preview	Updated
hyperframes	🟢 Ready	View Preview	Sep 17, 2026, 12:18 AM

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

[miga-heygen]

Holding the merge on this one. It publishes an engine capability that no render configuration can reach, so it would be followed by another release within the hour. Regenerating it once #4020 lands so the tag carries both commits and the notes can say plainly that the blur is opt-in and how to switch it on, instead of the current paragraph explaining that nothing can. Review is still useful; only the merge is held.

[somanshreddy]

APPROVE at 3ec17243 — clean release cut, verified it ships exactly what it claims and nothing else. Manual pass (codex disabled per workspace cap).

No stealth source change: the diff is purely release mechanics — 16 uniform 0.8.44→0.8.45 version bumps (13 package.json + 3 plugin manifests) + changelog.mdx + releases/v0.8.45.md. No .ts/source files touched.

Ships the claimed work, content-verified not prose-trusted: packages/engine/src/services/motionBlur.ts and MotionBlurAccumulator are present at the release head, and the v0.8.44...v0.8.45 compare range is exactly two commits — feat(engine): sub-frame multi-sample motion blur (#4019) + this release commit. So #4019 is genuinely in the release, and it's the only substantive change in the window.

Release notes are accurate and complete: the changelog entry documents the engine and correctly states it's dark-shipped — "Not yet reachable from a render… no render configuration sets that option yet, so there is no flag to turn it on. Wiring it through the producer follows in the next release." That matches reality: the switch (#4020) is still in review, so v0.8.45 ships the engine behind CaptureOptions.motionBlur with no activation path — no risk to existing projects, and a reader won't hunt for a flag that doesn't exist yet. Since the range is a single feature commit, the notes have no undocumented changes.

CI all green/pending, none red; BLOCKED is branch protection awaiting this stamp. Home to merge.

[miga-heygen]

Closing in favour of a fresh cut. This PR was prepared before #4020 merged, so its notes say the capability is unreachable from a render configuration, which is no longer true. Main now carries #4008, #4014, #4019, #4020 and #4022, and v0.8.45 is being re-cut on that head so the notes describe both motion blur mechanisms honestly.