Commit Graph
499 Commits
Author SHA1 Message Date
James RussoandClaude Opus 5.5 39347da9de fix(cli): leave files from outside the project out of Lambda and Cloud Run site uploads (#8060)
* fix(cli): leave files from outside the project out of Lambda and Cloud Run site uploads

A site upload for `lambda` or `cloudrun` followed every symlink in the project and
shipped what it pointed at, wherever that was on the machine. `publish` and `cloud
render` already ask first. Site uploads now leave a file or folder linked in from
outside the project out and name each one; `--include-outside-files` (or
`includeOutsideFiles` in the SDK's deploySite, renderToLambda and renderToCloudRun)
uploads them. publishProjectArchive called without a prepared archive now leaves
outside files out too, since nothing approved them.

— Rames

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(producer): drop the new option comments the comment ratchet refuses

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 09:25:25 +00:00
Miguel Ángel a6dd840eb1 chore: release v0.9.60 (#7994) 2026-11-17 01:59:35 +00:00
Miguel Ángel 028ab75535 chore: release v0.9.59 (#7973) 2026-11-17 00:10:38 +00:00
Miguel Ángel 725d13bb1d chore: release v0.9.58 (#7932) 2026-11-16 15:15:30 +00:00
Michael Wang 7aaeb93716 fix(producer): the plan copy checks every project entry, whatever its name (#7906)
* fix(producer): the plan copy checks every project entry, whatever its name

A top-level name that starts with two dots, such as ..assets, is an ordinary
project entry. The plan copy treated it as outside the project and skipped the
link-resolving containment check, so a link with such a name had its target
copied into compiled/. Only the project folder itself now skips the check, and
the outside test compares whole path segments.

* fix(aws-lambda,gcp-cloud-run): untar leaves out symbolic links and special files

A project archive can come from another person. A symbolic link in it could
point anywhere on the render host, and the planner would copy its target. Untar
now unpacks only files, folders and hard links. node-tar already keeps a hard
link's target inside the destination folder. The CLI's site upload follows
symbolic links when it packs, so its archives hold none.

* fix(aws-lambda,gcp-cloud-run): untar turns hard links into separate plain files

The site upload packs two hard-linked project files as one file and a hard
link. Untar still unpacks both, then gives each hard-linked file its own copy,
so the extracted project holds no links of any kind and loses no file.

* fix(aws-lambda,gcp-cloud-run): copy hard-linked files without mkdtemp; untar test in its own file

* fix(cloud): keep the hard-link copy name short so long file names still unpack
2026-11-16 06:38:08 +00:00
Miguel Ángel 1b29623f18 chore: release v0.9.57 (#7921) 2026-11-16 06:16:47 +00:00
Miguel Ángel 79990aed9a chore: release v0.9.56 (#7915) 2026-11-16 03:29:27 +00:00
Michael Wang 014326b40b fix: every composition file server refuses credential and tool-state files (#7889)
* wip: paused before review

* test: cover credential files on the preview routes and the deploy notice

* refactor: name the inspector's file lookup for what it serves

* fix(cli): a link to a private file outside the project keeps its own left-out reason

* fix: escape the upload notice and skip private files from old manifests
2026-11-16 01:42:08 +00:00
Miguel Ángel 894f0808b3 chore: release v0.9.55 (#7864)
* chore: release v0.9.55

* chore: release v0.9.55 notes include #7830

* chore: release v0.9.55 notes include #7859 and #7867

* chore: release v0.9.55 notes name the docs change and cloud render

* chore: release v0.9.55 notes include #7866 and #7801

* chore: release v0.9.55 notes match the style bar
2026-11-15 22:33:02 +00:00
Miguel Ángel 064c436557 chore: release v0.9.54 (#7850)
* chore: release v0.9.54

* chore: release v0.9.54 notes include #7827, #7825, #7845, #7848 and #7849

* chore: release v0.9.54 notes include #7853

* chore: release v0.9.54 notes include #7851 and #7855
2026-11-15 19:17:45 +00:00
Miguel Ángel ce18c3a102 chore: release v0.9.53 (#7841)
* chore: release v0.9.53

* chore: release v0.9.53 notes include #7836 and #7839

* chore: release v0.9.53 notes include #7840 and #7843
2026-11-15 15:50:38 +00:00
Michael WangandClaude Opus 5.5 55b5147098 fix: Cloud Run renders reach only public addresses; frame cache folder is private to its user (#7777)
* fix(gcp-cloud-run): render pages cannot reach the service's own dispatch endpoint

The Cloud Run image now sets PRODUCER_RESTRICT_PAGE_NETWORK=true, so a
rendered page reaches only its own project server and public addresses,
not loopback ports or the metadata server. The dispatch endpoint also
refuses any POST that carries an Origin header: browsers send one on every
POST and Cloud Workflows never does.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(engine): the default frame cache folder is private to the user who renders

The default extraction cache sits in the shared temp folder. It is now
created with mode 0700, an existing one owned by the same user is closed
to others (its entries stay, so cache hits carry over), and one that is a
link or belongs to another user is not used: that render runs without the
cache and prints a warning. The animated GIF cache under the same folder
follows the same rule. A folder set with HYPERFRAMES_EXTRACT_CACHE_DIR is
left as it is.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* feat(gcp-cloud-run): a Terraform variable turns the page network restriction off

restrict_page_network (default true) sets PRODUCER_RESTRICT_PAGE_NETWORK on
the service. The package README and docs say what the restriction refuses
and how to turn it off for trusted compositions that need private hosts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(engine): restore an unset TMPDIR as unset after the cache-root tests

Assigning undefined to process.env stores the string "undefined", so on a
runner with no TMPDIR every later test made its temp folder under ./undefined.

* test(engine): the frame-extractor link test also restores an unset TMPDIR as unset

* chore(engine): raise the packed size budget to 500000

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 06:34:11 +00:00
Miguel Ángel ad3a2389ee chore: release v0.9.52 (#7800) 2026-11-14 21:38:34 -05:00
Miguel Ángel cb15cb0e54 chore: release v0.9.51 (#7799) 2026-11-14 21:09:12 -05:00
Miguel Ángel 5e0577f124 chore: release v0.9.50 2026-11-14 19:39:50 -05:00
Miguel Ángel fd7217c8af chore: release v0.9.49 (#7767) 2026-11-14 18:15:46 -05:00
Miguel Ángel f33f137b2d chore: release v0.9.48 (#7761) 2026-11-14 17:04:22 -05:00
Miguel Angel Simon Sierra 2f46a88dea chore: release v0.9.47 2026-11-14 12:13:11 -05:00
Miguel Ángel 43132411c8 chore: release v0.9.46 (#7732) 2026-11-14 13:40:20 +00:00
Miguel Ángel fe8d93056c chore: release v0.9.45 (#7729) 2026-11-14 09:45:48 +00:00
Miguel Ángel 58ef24c6d8 chore: release v0.9.44 (#7708) 2026-11-14 06:22:47 +00:00
Miguel Ángel c727e890f2 chore: release v0.9.43 (#7664) 2026-11-13 22:42:53 +00:00
ClippyandClaude Opus 5.5 f01209d4ae fix(deps): bump tar, hono, @hono/node-server, adm-zip, sharp and postcss-selector-parser (#7656)
Raise the direct ranges so the workspace and published packages resolve
patched releases: tar 7.5.22, hono 4.13.16, @hono/node-server 2.1.6,
adm-zip 0.6.1, sharp 0.35.5 and postcss-selector-parser 7.1.7. The CLI's
on-demand sharp install moves to 0.35.5 with them.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 18:18:17 +00:00
Miguel Ángel 30c0935a24 chore: release v0.9.42 (#7655) 2026-11-13 17:54:21 +00:00
Miguel Ángel 20084cbe67 chore: release v0.9.41 (#7632) 2026-11-13 04:26:22 +00:00
Miguel Ángel f5476851dd chore: release v0.9.40 (#7617) 2026-11-12 21:52:46 +00:00
5bf361f524 fix(docker): Node 22.23.5 for the November 2026 security release (#7611)
Co-authored-by: Joel Gallardo <joel.gallardo@heygen.com>
Co-Authored-By: Claude <noreply@anthropic.com>

Co-authored-by: heygengenesis[bot] <262951085+heygengenesis[bot]@users.noreply.github.com>
2026-11-12 18:52:24 +00:00
Miguel Ángel 256675f92c chore: release v0.9.39 (#7605) 2026-11-12 13:27:37 +00:00
Miguel Ángel 1ec03c4e19 chore: release v0.9.38 (#7594)
* fix(scripts): release:prepare refuses a baseline that skips a release whose tag this clone lacks

* chore: release v0.9.38
2026-11-12 08:29:06 +00:00
terencechoandClaude Opus 5.5 e8e1177ad6 chore: release v0.9.37 (#7578)
* chore: release v0.9.37

* docs(release): add #7576 to v0.9.37 notes

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 02:01:41 +00:00
Vance Ingalls f66c673d19 chore: release v0.9.36 (#7575) 2026-11-11 16:06:36 -08:00
terencechoandClaude Opus 5.5 6bd9bb8a44 chore: release v0.9.35 (#7571)
* chore: release v0.9.35

* docs(release): note the render stop and container 403 from #7563 in v0.9.35

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-11 22:09:19 +00:00
Miguel Ángel 7a4dfb7654 chore: release v0.9.34 (#7555) 2026-11-11 16:46:12 +00:00
Miguel Ángel e596be16c9 chore: release v0.9.33 (#7543) 2026-11-11 06:32:08 +00:00
Miguel Ángel eb9092113d chore: release v0.9.32 (#7520) 2026-11-11 02:26:28 +00:00
PaprikaChenandClaude Opus 5.5 1a9fb8acb6 feat: opt-in 4:4:4 chroma for SDR MP4 masters (#5820)
* feat(engine): decouple transparent background from png capture format

PNG capture used to imply a cleared page background. A new
CaptureOptions.transparentBackground lets lossless opaque PNG capture
(4:4:4 MP4 output) keep the page background. Absent, it still follows
format === "png", so alpha output and motion blur are unchanged.

Opaque PNG skips drawElement, whose verification and worker-encode
paths are JPEG-only.

Refs #5555

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* feat(engine): add 4:4:4 chroma option to getEncoderPreset

getEncoderPreset takes an optional chromaSubsampling ("420" by
default). "444" returns yuv444p for SDR MP4, so libx264 encodes the
High 4:4:4 Predictive profile and odd sizes need no even padding.
WebM, MOV and HDR presets ignore it. The ChromaSubsampling type is
exported for the producer.

Refs #5555

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* feat(producer): chromaSubsampling render option with lossless png capture

RenderConfig.chromaSubsampling ("420" by default) opts an SDR MP4
render into 4:4:4. "444" encodes libx264 yuv444p and captures every
frame as opaque PNG: Chrome's quality-100 JPEG is already 4:2:0 on
beginFrame and screenshot capture, and drawElement can fall back to
screenshot mid-render, so PNG is the only capture that keeps the
colour. drawElement is turned off for these renders.

The probe and main capture options share resolveCaptureSurface, so
they cannot disagree on format, quality or background.

Formats other than mp4, GPU encoding and HDR output are rejected
before any work starts, auto-detected HDR sources fail before capture,
and distributed requests refuse 444. The default render is unchanged.

Refs #5555

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* feat(producer,studio-server): accept chromaSubsampling on render routes

The shared parseEncoderOptions validates chromaSubsampling and answers
400 for "444" with a non-mp4 format, gpu, or force-hdr, so a request
that would come back 4:2:0 never starts a render. The Studio render
route, both Studio adapters and the producer HTTP server forward it.
The producer server also refuses "444" with outputDynamicRange "hdr",
which parseEncoderOptions cannot see.

No Studio UI control; the option is route-level like crf and hdrMode.

Refs #5555

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* feat(cli): add --chroma-subsampling flag

`hyperframes render --chroma-subsampling 444` opts an SDR MP4 render
into full-resolution chroma (yuv444p with lossless PNG capture). The
default stays 420. The plan rejects 444 with a non-mp4 format, --gpu
or --hdr before anything renders, with a usage error that names the
conflicting flag.

The value reaches the local render request and, only when it is 444,
the Docker argv, so default Docker invocations are unchanged.

Refs #5555

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: document 4:4:4 chroma subsampling

Add a "4:4:4 masters" section to the rendering guide: when to use
--chroma-subsampling 444, why it captures PNG, the measured chroma gain
(large for text and UI, none for footage and gradients), its limits,
and a player compatibility table to be filled in from testing.

Document the flag in the CLI reference, the built-in rendering docs and
the hyperframes-cli skill reference (with the regenerated skills
manifest), and the chromaSubsampling option in the producer docs.

Refs #5555

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: add 4:4:4 player compatibility results

Fill the 4:4:4 compatibility table from testing H.264 High 4:4:4
Predictive output. Chrome 155, Edge 155, VLC 3.0, Safari on iOS 26.6
and Safari 26.6 on macOS play it, and so does AVFoundation on macOS
26.6, the framework QuickTime Player plays through. Firefox 157 on
Windows and both Windows media players do not.

Refs #5555

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: note the measured render cost of 4:4:4 output

Replace the vague "slower capture" note with measured numbers: a text
and UI composition rendered in about twice the default time, full-frame
footage in about three and a half times, because PNG encoding cost grows
with image detail.

Refs #5555

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(producer): reject chromaSubsampling 444 in distributed render config

Distributed configs have no chroma field and validateDistributedRenderConfig
ignored unknown keys, so a JS caller passing chromaSubsampling: "444" to the
Lambda or Cloud Run SDK got a 4:2:0 file with no error. Reject it, and make
the rendering guide say so precisely.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(producer): check a 444 render reaches the encoder as yuv444p

Every helper had tests, but nothing checked the orchestrator passes
chromaSubsampling through, so dropping it from the encoder preset or capture
surface would turn 444 renders back into 4:2:0 with all tests green. Render a
small fixture with "444" and with the default and check pix_fmt with ffprobe.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* refactor(producer): move the 444 drawElement gate into a helper

Keeps runCompileStage under the fallow complexity threshold.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore: keep comment share at or below the merge-base

comment-ratchet failed on 11 files this PR touched. Keep the 4:4:4
rationale once in chromaSubsampling.ts, move the distributed-render
reason into its error message, and cut the rest.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(producer): check a 444 render captures full-resolution chroma

The encoder check alone passes when chromaSubsampling is dropped from the
capture surface: frames are captured as JPEG and encoded yuv444p with
4:2:0 colour. Put a red/blue edge at an odd x, inside a 4:2:0 chroma
pair, and require the two pixels to differ in Cb.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(producer): trim the chromaSubsampling.ts header to the package comment share

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: finish switching to capturesAlpha from #6262

The merge that adopted main's transparent / capturesAlpha left these files
uncommitted, so resolveCaptureSurface still returned transparentBackground.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* refactor(engine): use transparent / capturesAlpha from #6262

main added CaptureOptions.transparent and capturesAlpha (#6262), which do
what this PR's transparentBackground did. Use them, keep the PNG check in
drawElementWorkerEncodeEligible, and re-pin test-classification.mjs and
the skills manifest against current main.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(producer): cut the 4:4:4 comment blocks to one to three lines

The reasoning lives in the PR description with the measurements.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* refactor: reconcile 4:4:4 chroma with latest main

Keep main's video-layer capture overrides, template entry resolution,
ProRes profile parsing and blur-differential tests alongside the chroma
option, and fold the encoder sub-parsers into one loop.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore: keep main's compile-stage tests and regenerate the skills manifest

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-11 00:20:55 +00:00
Miguel Ángel cf90054613 chore: release v0.9.31 (#7506)
* chore: release v0.9.31

* docs(release): keep the release build line neutral in the 0.9.31 notes
2026-11-10 19:56:45 +00:00
Miguel Ángel ad1a5eab29 chore: release v0.9.30 (#7494) 2026-11-10 12:14:01 +00:00
James RussoandClaude Opus 5.5 c6d243a2de fix(gcp-cloud-run): pin the base image and verify chrome-headless-shell and bun by sha256 (#7487)
The Cloud Run render image ran bun's remote install script, fetched
chrome-headless-shell through an unpinned npx package, and built FROM a mutable
tag. The base image is now pinned by digest; chrome-headless-shell and bun are
downloaded directly and checked against pinned sha256s before use.

— Rames Jusso

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-10 10:17:34 +00:00
Miguel Ángel b4c7f9cf7c chore: release v0.9.29 (#7483) 2026-11-10 08:45:45 +00:00
Vance Ingalls 58686a74c6 chore: release v0.9.28 (#7475) 2026-11-09 18:13:13 -08:00
Miguel Ángel 9e346f9bb7 chore(release): cut v0.9.27 (#7464) 2026-11-09 22:55:56 +00:00
Miguel Ángel 0c6c7fca45 chore: release v0.9.26 (#7421) 2026-11-08 23:36:46 +00:00
Miguel Ángel 327e20208c chore: release v0.9.25 (#7414) 2026-11-08 19:59:06 +00:00
Miguel Ángel 7ad2be96ea chore: release v0.9.23 (#7399) 2026-11-08 06:39:39 +00:00
Miguel Ángel 26956ea1f4 chore: release v0.9.22 (#7392) 2026-11-08 01:18:54 +00:00
Miguel Ángel a0bbaab436 chore: release v0.9.21 (#7385) 2026-11-07 22:51:28 +00:00
Miguel Ángel e206ff6bd9 chore: release v0.9.20 (#7358) 2026-11-07 10:56:20 +00:00
Miguel Ángel a9a8d89377 fix(engine): a render no longer finishes without an image that loaded late (#7304)
* fix(engine): a render no longer finishes without an image that loaded late

* style(engine): format the frame gate

* fix(engine): an image outside the frame no longer stops a render

* fix(engine): a render stops and warns when a frame's image never arrives, with no cloud retries

* fix(producer): a cloud chunk keeps the missing image's error name so retries stop
2026-11-06 20:11:01 +00:00
terencechoandClaude Opus 5.5 f54b2227fd feat(share): extract shared review kernel for local hosts (#7134)
* feat(share): extract shared review kernel for local hosts

* fix: recover completed shares and integrate kernel checks

* fix: terminate ffprobe options before share media input

* fix: verify executable imports without matching JSDoc types

* build: budget the published sharing package

* fix: publish NodeNext-compatible sharing declarations

* fix: invalidate shared renders when linked media changes

* fix: reserve share progress before awaiting upload lock

* fix: copy share build inputs before image dependency install

* fix(share): preserve Desktop snapshots and support portable locks

* fix(share): restrict video uploads to trusted origins

* fix(share): preserve review state across recovery and uploads

* fix(share): preserve review title and feedback attribution

* fix(share): accept legacy review records safely

* build(share): update measured package size budget

* fix(share): preserve feedback cutoff across export retries

* docs(share): describe only the storage origins the signer uses

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 04:35:33 +00:00