Skip to content

chore: release v0.9.63 - #8080

Merged
miguel-heygen merged 1 commit into
mainfrom
release/v0.9.63
Nov 17, 2026
Merged

miguel-heygen merged 1 commit into
mainfrom
release/v0.9.63

Conversation

@miguel-heygen

Copy link
Copy Markdown
Collaborator

What

Releases HyperFrames v0.9.63: the version bump across the published packages and plugin manifests, and its notes in releases/v0.9.63.md and docs/changelog.mdx. It carries every change listed for v0.9.62, which never reached npm, and is the first release published from its own commit within a merge-queue push (#8077), with npm trusted publishing alone (#8070).

No visible change

Version bump and changelog only. Each change below was reviewed, and where it shows, captured, in its own pull request.

Notes

Released on 2026-11-17.

Studio's sealed preview shows audio meters and audio groups, a layer reorder is one undo step again, and text films start sooner. No HyperFrames server serves a project file as a service worker's script. This release also carries every change listed for 0.9.62. That version never reached npm: the merge queue landed it in one push with another PR, and the publish read only the push's last commit. Since #8077 a release publishes from its own commit in the push.

Features

  • Core: The preview can stream an element's geometry to the editor every frame (f9c5ed07b, #8052).

Performance

  • Engine: Check still frames on several pages at once so text films start sooner (8ec97da01, #7997).
  • Producer: Frames start drawing while the audio mix finishes (0be1a0719, #7985).

Fixes

  • CLI, Producer, Inspector: Render, capture and inspector servers never serve a service worker's script (72925380c, #8073).
  • Studio: A layer reorder is one undo step again (df31ce2b1, #8072).
  • Studio: Audio meters and audio groups work in a sealed preview (93a4d29c0, #8011).
  • Studio: Adding a track no longer remounts every clip on the timeline (b064e40e1, #8068).
  • Studio Server: A project file is never served as a service worker's script (b4acc1a1d, #8064).
  • Studio: A service worker a project left behind is gone before a preview frame loads (7a0bec682, #8067).
  • Core: A held video picture is drawn through a VideoFrame closed after the draw (43e5b7cec, #7971).
  • Producer: Leave outside links out of site listings by default and warn SDK callers (fbb483852, #8065).

Internal

  • Publish: A release merged in one push with other PRs publishes at its own commit (9b565c8e0, #8077).
  • Publish: Publish to npm with the job's OIDC token, not a stored token (c106793f7, #8070).
  • Core: The reloaded-video playhead test builds a smaller film so busy CI never times it out (34f98e6a0, #8069).
  • Studio: The edit bench reads a sealed preview through its editing port (5f8b7a6ee, #8010).

Full changelog

v0.9.61...v0.9.63

@mintlify

mintlify Bot commented Nov 17, 2026

Copy link
Copy Markdown

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

Project Status Preview Updated
hyperframes 🟢 Ready View Preview Nov 17, 2026, 3:45 PM

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

@jrusso1020 jrusso1020 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need: none. APPROVE at 3bdbfc18.

This is a release-only diff: 22 files, all version bumps plus releases/v0.9.63.md and docs/changelog.mdx. There is no code change.

Versions: the 15 publishable packages/* and all five plugin/extension manifests are at 0.9.63. The private sdk-playground correctly stays where it was. The only remaining 0.9.61/0.9.62 strings are fixtures in scripts/publish-workflow.test.mjs.

Ancestry: HEAD contains the 0.9.62 release commit (fbcdf4c), #8072 and the publish fix #8077 (9b565c8). The base is current main.

Notes: they cover every commit from the v0.9.61 tag up to the base, so users jumping from 0.9.61 straight to 0.9.63 see everything 0.9.62 was meant to ship. They say plainly that 0.9.62 never reached npm, and the compare link runs v0.9.61 to v0.9.63. release-only-diff.mjs --verify passes locally, and the Release checks job passed.

Publish path: .github/ matches main, so this run uses #8077's scan over the whole push range. The release publishes whether or not the merge queue batches it with other PRs. Nothing in publish.yml assumes 0.9.62 is on npm or tagged: the only npm view is the idempotency skip for @0.9.63, and the release body comes from releases/v0.9.63.md.

Nits, not blocking:

  • docs/changelog.mdx still lists v0.9.62 as "Released 2026-11-17", though it never published.
  • The notes could link releases/v0.9.62.md, but its content is already merged in.

Build was still running when I posted, so the merge waits on that.

Review by Rames

@miguel-heygen
miguel-heygen added this pull request to the merge queue Nov 17, 2026
@mintlify

mintlify Bot commented Nov 17, 2026

Copy link
Copy Markdown

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

Project Status Preview Updated
hyperframes 🟡 Building – Nov 17, 2026, 3:41 PM

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

Merged via the queue into main with commit e865947 Nov 17, 2026
70 checks passed
@miguel-heygen
miguel-heygen deleted the release/v0.9.63 branch November 17, 2026 16:11

This branch was successfully deployed

1 active deployment
staging - docs — 3bdbfc18 Deployed Nov 17, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants