[vanceingalls]

What

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

Why

Ships HF_VIDEO_FRAME_WINDOW (#7240, #7241, #7242), which HyperFrames Desktop needs for long exports, plus the drawElement sample check (#7255) and the other fixes on main since v0.9.16.

No visible change

Version bump only. It has no UI change of its own.

Package size budget

@hyperframes/producer unpacked goes from 3,081,613 to 3,130,000 bytes. This build measured 3,112,478, which is 49 bytes past the 1% tolerance, from the windowed frames modules plus the version bump. The tarball is dist/ only, with no tests or source maps in the local build.

Test plan

• bun run release:prepare 0.9.17 passed, and the release notes were reviewed.
• Before cutting this, the windowed route passed a drawElement render on current main with the fix(producer): segmented and sequential capture check drawElement samples #7255 sample check live. Breaking the truth-page hook made it fall back, so the check does read windowed frames.
• CI on this PR.

🤖 Generated with Claude Code

[mintlify]

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

Project	Status	Preview	Updated
hyperframes	🟢 Ready	View Preview	Nov 5, 2026, 7:37 PM

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

[github-actions]

Edit accuracy: accurate 267 (base branch 267), smooth 130 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 (8)

• seqplainkeys-none-center-r0-nested-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): pass, passes
• seqplainkeys-none-center-r0-root-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): pass, passes
• seqplainkeys-none-center-r30-root-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): not run
• seqplainkeys-none-pct-r0-root-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): pass, passes
• seqplainkeys-none-pct-r30-root-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): not run
• seqplainkeys-none-px-r0-nested-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): fail / pass / pass, passes
• seqplainkeys-none-px-r30-nested-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): not run
• seqplainkeys-none-px-r30-root-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): not run

Unstable (1)

• seqplainkeys-none-pct-r0-nested-z100: tracking 0.05, pressJump 0, drop 0, reload 0, render 0.02, renderKey -, undo false, teleport true / tracking 0.05, pressJump 0, drop 0, reload 0, render 0.02, renderKey -, undo true, teleport true / tracking 0.05, pressJump 0, drop 0, reload 0, render 0.02, renderKey -, undo true, teleport true

[heygengenesis]

Verdict: COMMENT (post-merge) · 0 blocker · 0 important · 0 nits · 15445edf — Ready

Post-merge advisory review. This PR is already merged into main as 32eb4c35, so nothing here gates. I found nothing to follow up on.

What I checked

• No late merges. The base is the tip of main at 968f97fe (#7242). The merge commit's tree matches the head exactly, and nothing landed on main after the cut.
• Notes. I re-ran draft-changelog.ts 0.9.17 --from v0.9.16 --to 968f97fe. It gives 23 bullets, and they match releases/v0.9.17.md and the mdx <Update> block exactly. The summary matches the code and docs/packages/cli.mdx: the flag reads true, it applies only to segmented mp4/mov renders, and frames are deleted per segment.
• Bump. All 19 manifests are at 0.9.17 (14 packages and 5 plugin manifests in set-version.ts). Only the private sdk-playground is left out.
• Prerequisites. None of the 22 included PRs mentions a merge hold or a release prerequisite. #7242's known gap, that segmented capture never checks self-verify samples, is closed by #7255, which merged first.
• 15445edf (size budget). main's push CI at 968f97fe was red on Build for this reason. This PR is no longer release-only, so Release checks skipped and the full required suite ran instead. CI was green on this head. I checked the manifests by hand instead, and publish.yml keys only on the release/v head ref.