chore: release v0.8.0

[jrusso1020]

What

Release HyperFrames v0.8.0 from current main.

• Bumps all 13 publishable packages and three plugin manifests from v0.7.111 to v0.8.0.
• Documents v0.8.0 as the supported minor-version boundary for Plan v2 becoming the default distributed cloud transport.
• Includes the catalog-only removal from chore(catalog): remove two AI UI items #3317, the sole commit after v0.7.111.

Why

PR #3311 changed the behavior of an omitted planProtocol from Plan v1 to Plan v2. That behavior shipped in v0.7.111, but it warrants a minor-version boundary rather than another 0.7 patch.

The release notes are explicit that v0.8.0 adds no further cloud runtime delta beyond v0.7.111 and that users must redeploy matched-version cloud infrastructure before upgrading SDK callers.

How

Prepared with the repository's stable release workflow. The publish workflow will use the immutable merge SHA, create v0.8.0, publish npm packages to latest, and create the GitHub release only after this PR is approved and merged.

Test plan

• Unit tests added/updated
• Manual testing performed
• Documentation updated (if applicable)

Validation completed locally:

• bun run test:scripts: 182 Node tests and 29 catalog Vitest tests passed.
• bunx oxfmt --check docs/changelog.mdx releases/v0.8.0.md passed.
• Release commit guard accepted only version manifests and reviewed changelog artifacts.

No internal service, staging, or production deployment is part of this PR.

[mintlify]

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

Project	Status	Preview	Updated (UTC)
hyperframes	🟢 Ready	View Preview	Aug 17, 2026, 11:52 PM

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

[vanceingalls]

Review — hyperframes v0.8.0 release PR

Verified independently against GitHub (not just the Slack summary):

Diff scope: clean. Confirmed head f082a2e6c. All 17 changed files are version-bump-only: 3 plugin manifests + 13 packages/*/package.json (0.7.111→0.8.0), docs/changelog.mdx, and new releases/v0.8.0.md. Zero source/logic changes. No lockfile touch needed since internal deps use workspace:* protocol. Cross-checked #3317 (the claimed sole prior source change) — merged, catalog-only (2 component deletions + a data-only ALLOWED_DELETIONS allowlist entry, no logic change). Changelog and release notes match the diff and cite #3317 correctly. Version strings are consistent across all 16 files, no stray pre-release tags.

Blocker — this cannot merge via required checks as currently configured. The branch ruleset requires a literal regression status context. On this PR, only the regression-shards (shard-N, ...) matrix jobs post — there is no aggregate regression check anywhere in the rollup. Comparing to #3317 (merged): it posted both regression (COMPLETED) and regression-shards (single COMPLETED entry, effectively skipped). It looks like the workflow only emits the consolidating regression check on the skip path — when the full shard matrix actually runs (as here), the aggregate never posts. If that's right, regression will never go green on this PR regardless of shard outcomes, independent of code correctness.

Also as of this review: 2 shards (shard-2, shard-8) and the Windows test lane are still in progress, and this has 0 reviews / mergeStateStatus: BLOCKED.

Recommendation: code content is good — no objection to it on its own. But do not merge on green-required-checks alone once shards finish; someone needs to confirm the regression aggregate will actually post, or update the ruleset to key off the regression-shards matrix contexts instead. Flagging to James since this affects the release ruleset, not the release content.

— Vai

[jrusso1020]

Follow-up on the required regression context: this was a timing race, not a ruleset deadlock. After shard-2 and shard-8 completed successfully, the aggregate job appeared and passed at 2026-08-18T00:03:49Z (job 95549537779): https://github.com/heygen-com/hyperframes/actions/runs/32082104002/job/95549537779

gh pr checks --required now reports regression passing. The only remaining required context is Tests on windows-latest, which is still in progress. No ruleset or workflow change is needed.

[vanceingalls]

Confirmed independently — regression now shows SUCCESS (run 32082104002/job 95549537779), and all 8 required checks (Build, Render on windows-latest, Semantic PR title, Test, Test: runtime contract, Tests on windows-latest, Typecheck, regression) are green on head f082a2e6c, same SHA reviewed earlier. That resolves the only blocker I flagged.

Diff content was already verified clean in my earlier review (pure version-bump release, no source changes beyond already-merged #3317). Approving.

— Vai

[miguel-heygen]

Post-merge advisory review (this PR is already merged into main). No follow-up findings.

Audited exact PR head f082a2e6c90dd53a61ddd855ac33afbc866381aa and merge commit 232686f7e077e16d4495ed623a5eb5e16cb72f0e.

• The PR diff is exactly the stable-release allowlist: 13 publishable package versions, three plugin versions, docs/changelog.mdx, and releases/v0.8.0.md.
• All package/plugin manifests are 0.8.0; no reviewed-summary TODO markers remain.
• The range after v0.7.111 contains only catalog cleanup #3317 plus this release commit. There is no hidden cloud runtime delta.
• The migration copy correctly states that Plan v2 already shipped as the omission default in 0.7.111, requires matched-version AWS/GCP infrastructure before SDK callers, and preserves explicit v1 compatibility.
• All eight required ruleset contexts completed successfully. The delayed regression aggregate appeared after its shards and passed; no workflow or ruleset change was needed.
• Remote tag v0.8.0 points at the exact merge commit. The immutable publish workflow is currently in progress.

Verdict: COMMENT (post-merge: Ready)
Reasoning: The release content, semver boundary, migration guidance, tag target, and required gates all match the repository's stable-release contract; I found no residual issue to follow up.

— Magi