[miguel-heygen]

Release v0.8.190: version bump to 0.8.190 in every package and plugin manifest, the release notes in releases/v0.8.190.md, and the matching entry in the docs changelog.

Since v0.8.189 it ships a preview seek bar in Studio, render -c taking an absolute entry inside the project, one frame-cache budget shared by the capture workers, a thumbnail capture page that loads media near the playhead like the preview, long audio mixes that load their clips a few at a time, and an AWS Lambda audio function that warms while the plan runs.

Merging this PR runs the Publish workflow, which creates the v0.8.190 tag at the merge commit, publishes the npm packages and creates the GitHub release. No tag is pushed by hand.

No visible change

Version numbers and release notes only. No code changes in this PR.

[mintlify]

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

Project	Status	Preview	Updated
hyperframes	🟢 Ready	View Preview	Oct 23, 2026, 9:37 PM

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

[heygengenesis]

Verdict: REQUEST CHANGES · 1 blocker · 0 important · 0 nits · head 54e1fd28

The version bump is complete: 19 manifests went from 0.8.189 to 0.8.190, and no 0.8.189 is left outside the notes. The notes match the 6 commits from v0.8.189 to this branch's base fb2f7c1a8. The problem is that main has already moved past that base (inline).

Scope

Read the full diff, compared v0.8.189..54e1fd28 with the notes, and read publish.yml's tag step (it tags merge_commit_sha) and the main ruleset (squash merge queue, required checks not strict). CI was still running at review time.

[heygengenesis]

blocker: #6107 (4ed781338, "feat(core): capture blur falls back to per-element filters where capture cannot run") merged to main at 20:46 UTC, after this branch's base fb2f7c1a8. The ruleset doesn't require branches to be up to date and merges through a squash queue, and publish.yml tags merge_commit_sha. So v0.8.190 will include #6107 while neither this file nor docs/changelog.mdx lists it, and the GitHub release body comes from this file. Rebase onto main and add a Core feature line for #6107 in both files. If you'd rather hold #6107 back, the release has to be cut from fb2f7c1a8 instead of going through the queue.

[github-actions]

Edit accuracy: accurate 271 (base branch 271), smooth 126 of those

The gate passes.
Smoothness is reported in the artifact, not gated. A case fails only if it fails 2 of 3 runs.

Quarantined, measured but not gated (0)

Unstable (1)

• seqheldtwice-tlhold-px-r0-root-z100: tracking 120.29, pressJump 312.3, drop 0, reload 0, render 0.02, renderKey -, undo true, teleport false / tracking 0.41, pressJump 0.11, drop 0.35, reload 0.35, render 0.02, renderKey -, undo true, teleport true / tracking 0.41, pressJump 0.11, drop 0.35, reload 0.35, render 0.02, renderKey -, undo true, teleport true

[heygengenesis]

Verdict: APPROVE — 1 resolved, 0 open, 0 new · 54e1fd28 → c8fd6c7c

The branch is now based on current main (79b57ab12). The notes and the docs changelog list all 11 commits in v0.8.189..c8fd6c7c^, every commit link resolves, and the 19 manifests are at 0.8.190. One wording note that doesn't block: the #6108 line has no area label and doesn't mention motion blur.