chore: release v0.7.72

[jrusso1020]

Summary

• release HyperFrames 0.7.72 across all fixed-version packages and plugin manifests
• publish the merged Plan v2 producer API required by object-storage-backed Temporal workers
• include reviewed release notes for the complete v0.7.71...v0.7.72 range

Why

@hyperframes/producer@0.7.71 does not export the Plan v2 manifest, publisher, or integrity APIs. The merged producer work on main does, so the internal distributed-rendering integration must consume a real published 0.7.72 rather than a local checkout.

Plan v2 is designed for independently scheduled workers: content-addressed artifacts and the manifest are exchanged through object storage. Local disk remains pod-local scratch and is never a cross-node contract.

Verification

• repository script tests: 15 suites passed; packed-manifest fixture: 9/9 passed outside the filesystem sandbox
• bun run format:check
• release channel validation for release/v0.7.72 → latest
• git diff --check

Merging this release/v0.7.72 PR triggers the standard npm publish workflow.

[jrusso1020]

• chore: release v0.7.72 #2800 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[mintlify]

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

Project	Status	Preview	Updated (UTC)
hyperframes	🟢 Ready	View Preview	Jul 26, 2026, 5:37 AM

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

[vanceingalls]

Version bump is clean across all 16 fixed-version manifests, and the released Plan v2 surface matches James's claims exactly — verified against source and the locked export test, not just the PR description. APPROVE.

Version bump

Producer + monorepo consistency

All 13 package package.json files and all 3 plugin manifests bump 0.7.71 → 0.7.72 in lockstep, no stragglers:

• packages/{aws-lambda,cli,core,engine,gcp-cloud-run,lint,parsers,player,producer,sdk,shader-transitions,studio-server,studio}/package.json:3
• .claude-plugin/plugin.json:4, .codex-plugin/plugin.json:4, .cursor-plugin/plugin.json:5

No bun.lock change accompanies this — verified this is correct, not an omission: every internal @hyperframes/* dependency in bun.lock is pinned via workspace:* / workspace:^ protocol (e.g. packages/producer/package.json deps on @hyperframes/core, @hyperframes/engine, etc.), which resolves locally regardless of the package's own version digit. A lockfile update is not required for this bump.

Public exports

Exports match claims

Pulled packages/producer/src/index.ts and packages/producer/src/distributed.ts at 8c5c00f39 directly:

• planV2WithPublisher — exported from both the main entry (index.ts, distributed-primitives re-export block) and @hyperframes/producer/distributed (distributed.ts).
• PlanV2IntegrityError — exported from both entry points.
• PlanV2ArtifactPublisher (the "Publisher interface" referenced in the task/PR) — exported as a type from both entry points.
• LocalPlanV2ArtifactPublisher — exported only from @hyperframes/producer/distributed, deliberately not re-exported at the main index. This is not a gap: index.ts explicitly documents "the full surface lives at @hyperframes/producer/distributed," and packages/producer/src/services/distributed/publicExports.test.ts locks exactly this asymmetry — its "@hyperframes/producer/distributed (subpath)" describe block asserts typeof distributedSubpath.LocalPlanV2ArtifactPublisher === "function", while the "@hyperframes/producer (main entry)" block never asserts it on producerIndex. Design intent, test-locked, consistent.
• packages/producer/package.json exports/publishConfig.exports both declare ./distributed as a public subpath (import/types mapped to dist/distributed.{js,d.ts} post-build) — so this is a real, npm-resolvable public entry point, not an internal escape hatch.

Cross-checked against the two downstream consumers this release unblocks: #2795 (feat(aws-lambda): publish plan v2 directly to S3) and #2799 (feat(gcp-cloud-run): publish plan v2 directly to GCS) both import planV2WithPublisher, LocalPlanV2ArtifactPublisher, PlanV2ArtifactPublisher, PlanV2PublishBlob, plan, planV2, renderChunk from @hyperframes/producer/distributed — every symbol they need is present at head.

No surface leak

This PR's diff (gh api .../pulls/2800/files, cross-checked against compare/main...8c5c00f39 for parity — no hidden status: removed entries) touches exactly 17 files: 16 version bumps + docs/changelog.mdx + releases/v0.7.72.md (new). Zero source files changed. The Plan v2 export surface was already merged to main via #2777, #2788, #2792 (and adjacent #2789/#2790) in prior, separately-reviewed PRs; #2800 only publishes what's already there. No new exports are introduced by this PR to audit for leakage.

Changelog / release notes

docs/changelog.mdx and releases/v0.7.72.md both document the release with matching content (Features / Fixes / Catalog / Internal sections), citing commit SHAs and PR numbers (#2789, #2777, #2790, #2788, #2792, etc.) for every Plan v2-related change. One gap: neither document names the actual exported symbols (planV2WithPublisher, LocalPlanV2ArtifactPublisher, PlanV2IntegrityError) verbatim — bullets are prose ("Add remote-ready plan v2 publisher," "Document read-only plan hashing"). Checked releases/v0.7.71.md for precedent: same terse-prose convention, no symbol names there either. Not a deviation this PR introduced — nit, not a blocker.

Fresh 4-lens pass at 8c5c00f

Standards

No code changes present — exactly what a release PR should look like. The 17 changed files are limited to version fields + changelog/release-notes docs. Confirmed via both the Files API and compare/main...HEAD.

Spec forward-check

PR body claims (bump to 0.7.72, release merged Plan v2 APIs, unblock Temporal integration) all check out against the diff and the live export surface as verified above.

Spec reverse-check

Every changed file is accounted for by the "release" contract (package.json/plugin.json version bumps, CHANGELOG/releases/*.md) — no undisclosed file changes outside that set.

Sibling-precision (monorepo version consistency)

All 16 manifests agree on 0.7.72. No straggler left at 0.7.71.

Middle-man

N/A for a release PR.

Blast-radius / semver compliance

No breaking change ships under this bump — because no code ships under this bump at all; the Plan v2 additions are purely additive new exports, already merged and already covered by publicExports.test.ts, which also spot-checks that pre-existing in-process exports (executeRenderJob, createRenderJob, createCaptureSession, createFileServer) are unchanged. Repo convention (confirmed against v0.7.71.md, which also shipped a "Features" section under a patch-digit bump) is to bump only the third digit regardless of feature vs. fix content — this PR is consistent with that existing pattern, not a new deviation.

CI state

mergeable_state: blocked — decomposed via GraphQL: reviewDecision: REVIEW_REQUIRED, mergeable: MERGEABLE. This is a reviewer-gate, not a CI-gate. All completed checks pass (Typecheck, Lint, Format, CodeQL, Producer unit/integration tests, CLI smoke, Perf suite, Windows render/test lanes, etc.). 5 of 8 regression-shards jobs are still in_progress at time of review — none have failed. No required check is red; nothing in the PR body needs to explain a failure that doesn't exist.

Verdict

APPROVE
Version bump is clean and monorepo-consistent, the released Plan v2 surface (verified against source + the locked publicExports.test.ts, not just the PR description) matches every claim including the deliberate main-vs-subpath export split, and this PR itself carries zero code risk since it's pure version/changelog — recommend confirming the remaining regression-shards finish green before merge, but that's a wait-and-check, not a blocker.

— Via

[mintlify]

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

Project	Status	Preview	Updated (UTC)
hyperframes	🟡 Building	–	Jul 26, 2026, 5:36 AM

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

[james-russo-rames-d-jusso]

LGTM at 8c5c00f39. Version bump is clean:

• All 14 workspace package.json files bump from 0.7.71 → 0.7.72 consistently.
• The three plugin manifests (.claude-plugin/plugin.json, .codex-plugin/plugin.json, .cursor-plugin/plugin.json) also bump.
• releases/v0.7.72.md and the new entry in docs/changelog.mdx are the same content — release notes and changelog stay in sync.

Verified the "unblocks Temporal sidecar" claim: at 8c5c00f39, packages/producer/src/index.ts re-exports planV2WithPublisher, publishPlanV2FromV1, PlanV2IntegrityError, PlanV2ArtifactPublisher, PlanV2PublishBlob, and packages/producer/src/distributed.ts additionally re-exports LocalPlanV2ArtifactPublisher + LocalPlanV2ArtifactPublisherOptions. That surface landed in merged #2792 (which shipped after 0.7.71 was cut), so 0.7.71 genuinely doesn't have it and 0.7.72 genuinely does. The internal Temporal sidecar can now depend on @hyperframes/producer@0.7.72.