[miguel-heygen]

v0.8.182 was tagged but never reached npm: its publish stopped at the package size check (fixed by #6017). This release ships everything listed for v0.8.182, plus #6013, #6015, #6016 and #6017.

Website capture now handles pages that reload after a cookie banner, CLI commands start faster, a repeat check starts with the CLI and Chrome already up, and snapshot and check wait for late images as render does. Renders inside a macOS sandbox no longer fail, a sharp sound at a film's start no longer grows louder with each audio pass, and lambda sites create takes source files over 5 GB. Cloud renders mix their audio beside the chunks and fail loudly when an audio read is cut off, a 4K camera shown small reaches Chrome near the size it is drawn, a finished capture exits even when a site's DNS never answers, and an unreadable frame fails a render instead of shortening it.

Changes

• Versions bumped to 0.8.183 across the 14 published packages and 5 plugin manifests (release:prepare 0.8.183 --from v0.8.181 --no-tag).
• releases/v0.8.183.md: the v0.8.182 notes (42 PRs) plus fix(cli): a disk that fills mid-unzip fails the browser install at once instead of hanging #6013, fix(inspector): a component report names a snippet's file and lines only in its id #6016, fix(inspector): a component report shows the compositions and hosts that time a matched element #6015 and fix(aws-lambda): the size check on every PR measures the package a release publishes #6017, so 46 PRs, every one merged since v0.8.181. Checked against git log v0.8.181..main: none missing besides the v0.8.182 release commit itself.
• docs/changelog.mdx: the v0.8.182 entry becomes the v0.8.183 entry, with the same lines, the 4 additions and a sentence saying v0.8.182 never published. Users never got 0.8.182, so the changelog lists each change once, under the version that ships it. releases/v0.8.182.md stays as the record of the tag.

No visible change

Version bump and changelog only; each change was captured in its own PR.

[mintlify]

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

Project	Status	Preview	Updated
hyperframes	🟢 Ready	View Preview	Oct 21, 2026, 10:42 AM

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

[github-actions]

Edit accuracy: accurate 271 (base branch 271), smooth 163 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)

[vanceingalls]

Release audit at e53a423f (base ccc13c3b, the #6017 merge, which is the current tip of main). There are no other reviews.

Version bumps (19/19)

• All 14 published packages are at 0.8.183 at head: aws-lambda, cli, core, engine, gcp-cloud-run, inspector, lint, parsers, player, producer, sdk, shader-transitions, studio-server and studio.
• All 5 plugin manifests are at 0.8.183: .claude-plugin, .codex-plugin, .cursor-plugin, gemini-extension.json and the root plugin.json.
• The only packages/* manifest not bumped is sdk-playground, which is private (0.6.106).
• No 0.8.181 or 0.8.182 string remains outside the changelog and release notes. Every internal dependency uses workspace:.

Release notes and changelog

• git log --first-parent v0.8.181..ccc13c3b has 47 commits: 46 PRs plus the v0.8.182 release commit (#5955).
• Each of the 46 PRs appears in releases/v0.8.183.md, linked by its full merge SHA:
  • every short SHA matches its full SHA;
  • every PR number matches the subject of its commit;
  • the notes link no commit outside that range.
• #5943 has two entries, one under Fixes (Chrome exits with the CLI) and one under Performance (the warm check process). That is the same pair v0.8.182 had, one for each change it made.
• The bullets in the v0.8.183 docs/changelog.mdx entry match the release notes line for line. The compare link now points to v0.8.181...v0.8.183, and releases/v0.8.182.md is left as the record of the tag.

Size gate

• The v0.8.182 publish (run 39567705735) stopped at verify:packed-manifests with aws-lambda at 70170 packed and 254853 unpacked bytes. The budget was 70000 and 244000.

• #6017 changes three things:

  • every build writes prebuilt/template.yaml, so PR CI packs the template a release ships;
  • !scripts/*.test.ts keeps test files out of the tarball;
  • the budget moves to 70874 and 258166.

• Measured locally at this head, after a full bun run build:

  package	packed	unpacked
  as PR CI packs it	67626	245079
  as the release packs it	67725	245320
  headroom to the new budget	3149	12846

  The release row adds prebuilt/handler-zip.json as pin-handler-zip writes it, with the same fields and value lengths. There's no zip binary here, so I couldn't run build:zip. Pinning moves the zip out of dist/, so that file is the only one a release adds.

• Both sizes sit above the 85% floor (60242 and 219441) that would force the budget down.

Scope

• 21 files, +97/−21:
  • 14 package.json and 5 plugin manifests, one line each;
  • docs/changelog.mdx (+8/−2);
  • the new releases/v0.8.183.md (+70).
• Nothing else.

CI: the eight required checks are green at e53a423f: Build (which runs verify:packed-manifests, so the size gate passes in CI with the template packed), Render on windows-latest, Semantic PR title, Test, Test: runtime contract, Tests on windows-latest, Typecheck and regression. No check failed.

Verdict: APPROVE
Reasoning: Every published package and manifest is at 0.8.183. The notes list exactly the 46 PRs since v0.8.181, each once, with nothing extra. The package that failed v0.8.182's publish now measures 67725 and 245320 bytes, under the 70874 and 258166 budget.

— Via