613 Commits
Author SHA1 Message Date
Miguel Ángel 3ae9e7302d chore: release v0.9.68 (#8214) 2026-11-18 20:50:58 +00:00
Miguel Ángel 4a73363322 chore: release v0.9.67 (#8185) 2026-11-18 14:56:46 +00:00
Miguel Ángel 1a82f6e9d6 chore: release v0.9.66 (#8172) 2026-11-18 12:11:13 +00:00
James RussoandClaude Opus 5.5 61d65e7177 fix(aws-lambda): match the shell to its own pin, ship only hashed files, refuse the shell ZIP in CDK and SAM (#8173)
* fix(aws-lambda): match the shell to its own pin, ship only hashed files, refuse the shell ZIP in CDK and SAM

Review follow-ups to the pinned shell route:
- build-zip --source=chrome-headless-shell accepts the folder only when its
  digest is pinned for this version, not for any pinned build.
- It leaves out the files the digest skips (debug.log and chrome_debug.log,
  which Chrome writes as it runs), so nothing unhashed ships.
- The CDK construct throws on chromeSource "chrome-headless-shell" and the
  SAM template allows only sparticuz, as lambda deploy already refused it:
  a shell ZIP cannot fit a function. The CHROME_PATH wiring for that ZIP is
  gone with it.

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

* chore(aws-lambda): raise the packed size budget to 82,000 bytes

The shipped build-zip script now checks the shell against its own
version's pin and skips the files the digest leaves out. That takes the
tarball to 81,378 bytes in CI, over the 80,500 budget's 1% tolerance;
main was already within about 200 bytes of it.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 11:25:22 +00:00
James RussoandClaude Opus 5.5 ed3f05a05b fix(aws-lambda): pin the shell ZIP route, gate ZIP headroom, match arm64 fonts to x86 (#8170)
- build-zip --source=chrome-headless-shell stages only the repo's pinned
  build (managedChromeVersion) and only when its folder matches the pinned
  digest (isPinnedHeadlessShell), instead of the newest folder in the cache.
  The folder cannot fit a ZIP function, so lambda deploy refuses
  --chrome-source chrome-headless-shell up front on either arch, and the
  docs say the arm64 video image is where the shell runs.
- build-zip prints the headroom under the unzipped gate, and a new
  "Lambda handler ZIP" workflow builds the ZIP on PRs that touch the code
  it bundles, so growth fails before merge rather than in the release job.
- The arm64 image keeps @sparticuz/chromium's fonts and fonts.conf from the
  handler ZIP (FONTCONFIG_PATH=/var/task/fonts) instead of liberation-fonts,
  so text falls back to the same fonts as on x86. The image workflow renders
  a mixed-script page on both arches and fails when any line resolves to
  different platform fonts.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 10:21:01 +00:00
James RussoandClaude Opus 5.5 81d73d2278 fix(aws-lambda): chrome-headless-shell 158 in the arm64 video image, sparticuz 153 in the x86 ZIP (#8155)
* fix(aws-lambda): run chrome-headless-shell 158 in the arm64 video image

The arm64 video image now installs Chrome for Testing's linux-arm64 chrome-headless-shell
158.0.8127.36, pinned by sha256 and fetched with curl -f, as the whole shell folder. The Lambda
Node 22 base has none of the shared libraries the shell links and no fonts, so the image installs
them from the base's repository at the same pinned release. The image sets
HYPERFRAMES_LAMBDA_CHROME_SOURCE and HYPERFRAMES_LAMBDA_CHROME_PATH itself, and the nested video
function no longer passes ChromeSource, which would override them. stage-arm64-image.ts stops
fetching the sparticuz arm64 pack and drops the ZIP's x86 sparticuz Chrome instead.

The x86 handler ZIP stays on @sparticuz/chromium, bumped from 148.0.0 to 153.0.0. It builds at
258,502,222 bytes unzipped, under Lambda's 262,144,000-byte limit and the 248 MiB in-house gate.

Two fixes for --source=chrome-headless-shell:
- build-zip.ts staged only the executable, which exits at launch without its ICU data and .pak
  files. It now stages the whole shell folder at chrome-headless-shell-linux64/.
- Nothing set HYPERFRAMES_LAMBDA_CHROME_PATH, which src/chromium.ts requires for that source.
  The SAM template and the CDK stack now set it to the bundled shell when ChromeSource asks for it.

Drops the unused @types/aws-lambda devDependency, which the dead-code audit reports whenever this
package's manifest changes.

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

* ci(publish): build the Lambda arm64 video image on an ARM runner

The video stage now installs Chrome's system libraries with microdnf, so it runs code for arm64.
The pack job built that image on ubuntu-latest with no emulation, which it could do only while the
stage copied files. A new lambda-video-image job builds it natively on ubuntu-24.04-arm, from the
handler zip whose sha256 the zip job reported, and reports the OCI tarball's sha256. Pack downloads
that tarball, checks the sha256 against the job's, and pins it as before.

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

* chore(aws-lambda): fit the comment ratchet and the package size budget

chromium.ts loses the two doc lines on BUNDLED_SHELL_DIR and BUNDLED_SHELL_PATH; the names and the
SAM template's comment already say what they are.

@hyperframes/aws-lambda's unpacked budget goes from 290,508 to 298,000 bytes. The package unpacks to
295,324 bytes, up from the shared chrome-headless-shell staging module the ZIP and image scripts now
import and from the README and docs that describe the two Chrome sources.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 09:07:46 +00:00
James RussoandClaude Opus 5.5 7930525024 build(chrome): pin chrome-headless-shell 158.0.8127.36 wherever the repo installs it (#8145)
The engine ceiling moves from Beta 152.0.7977.30 to stable 158.0.8127.36, with its Chrome for
Testing digests. The places that installed `@stable` or an older pin follow it: the CI test
workspace, the regression test image, the k8s and Cloud Run examples, the CLI render image
(amd64) and the Lambda build hint. The motion-blur nightly keeps its pinned-versus-stable
comparison: the pin leg now uses the workspace's pinned shell, and a stable leg fetches stable.

The chat regression golden is regenerated on 158. Chrome 157 renders it pixel-identically to
158, so the previous golden recorded Chrome 152's paint of a background-clip:text phrase whose
word spans start at opacity 0.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 07:17:16 +00:00
Miguel Ángel 32ff8b3323 chore: release v0.9.65 (#8121) 2026-11-17 23:19:45 +00:00
Miguel Ángel f291b12598 chore: release v0.9.64 (#8097)
* chore: release v0.9.64

* chore: list #8090 and #8092 in the v0.9.64 notes
2026-11-17 18:25:31 +00:00
Miguel Ángel e86594759c chore: release v0.9.63 (#8080) 2026-11-17 15:55:44 +00:00
Miguel Ángel fbcdf4cad7 chore: release v0.9.62 (#8075) 2026-11-17 14:15:36 +00:00
Miguel Ángel 3599623f92 chore: release v0.9.61 (#8051) 2026-11-17 10:56:12 +00:00
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
Michael Wang 1463158a4b fix(lambda): uploads go only to a bucket the state machine's account owns (#7983)
The lambda commands read the bucket and state machine from
.hyperframes/lambda-stack-<name>.json, which arrives with any project
someone sends. A file naming another account's bucket made render,
render-batch and sites create upload the project there.

- renderToLambda pins ExpectedBucketOwner to the state machine ARN's
  account on every S3 request; deploySite takes expectedBucketOwner,
  which sites create and render-batch pass.
- The state file is read only as a plain file in a real .hyperframes
  folder, and its bucket, ARN, region and other fields are checked.
2026-11-16 23:17:54 +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
Michael Wang 11a7d2749d ci(publish): the release keeps only Lambda assets npm pins or this run built (#7880)
The pack job no longer downloads Lambda assets already attached to the
release; it always pins the handler zip and video image this run built.

The publish job decides what the release keeps. Once
@hyperframes/aws-lambda is on npm for the version, the release must hold
exactly the assets that package pins. Before then, an asset this run did
not produce fails a first attempt, and a re-run of the same workflow run
replaces it. An asset identical to the bundle's is left alone, so a
re-run of only the publish job also works.
2026-11-16 03:45:25 +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 d9488119be fix(aws-lambda): the release ships the arm64 ffmpeg only when it matches its committed digest (#7872)
* fix(aws-lambda): the release ships the arm64 ffmpeg only when it matches its committed digest

* style(ci): format the release workflow tests
2026-11-16 01:09:58 +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
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 e8a59bf177 fix(aws-lambda): Lambda renders reach only public addresses unless the function opts out (#7780)
* fix(aws-lambda): Lambda renders reach only public addresses unless the function opts out

* chore(aws-lambda): drop a comment the function name already says
2026-11-14 19:39:09 -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
ClippyandClaude Opus 5.5 9d1e4e54a7 fix(deps): bump puppeteer to 25.13 so chromium-bidi resolves zod 4.6.7 (#7652)
puppeteer-core 25.13.0 moves chromium-bidi to 157.0.8090-0, which depends on
zod ^4.6.5 instead of ^3.24.1. Lifts the engine/producer puppeteer pin from
~25.11.0 to ~25.13.0, keeps one puppeteer-core and one @puppeteer/browsers
(3.2.4) across the workspace, and updates both Lambda runtime locks with a
targeted npm resolution so only the puppeteer subtree changes.

Clears GHSA-mrhx-c7xc-m3w5 in both runtime locks.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 17:30: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
James RussoandClaude Opus 5.5 84799bdc59 fix: take helper programs only from install locations, never the project folder (#7524)
* fix(cli,parsers): take helper programs only from install locations, never the project folder

FFmpeg, FFprobe, whisper-cli, parakeet-mlx, Python and system Chrome are now
found through one shared rule: an absolute PATH entry outside the working
directory, or a fixed install dir. A relative PATH entry and any folder
inside the working directory are skipped, on every platform. Windows walks
PATH itself instead of asking `where`, which lists the working directory
first.

FFmpeg discovery no longer falls back to `.hyperframes/bin` or to an
installer package in the project's node_modules; an installer package
installed next to HyperFrames still works. The env overrides are unchanged.
The CLI skill reference stops suggesting the project-local folder.

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

* test(cli): give the PATH-lookup tests a fixed PATH on Windows

Windows now walks PATH instead of running `where`, so tests that faked
`where` output found the runner's real python and cmake. Both tests now set
PATH to a temp folder holding only the programs they expect.

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

* fix: report a missing helper program instead of running it by bare name

When no trusted FFmpeg or FFprobe is found, the engine, the producer's
probes and Studio's waveform, peak and audio-track helpers now report
"not found" with the HYPERFRAMES_FFMPEG_PATH / HYPERFRAMES_FFPROBE_PATH hint
instead of handing the bare name to the OS lookup. Callers that degraded
on a missing binary still do: runFfmpeg returns a spawn_error result, the
GPU and version probes report none, and Studio's audio helpers fail soft.

The Lambda handler names its bundled ffmpeg and ffprobe by path, since
they live under the task root, which is the working directory.

brew, git and cmake for the whisper.cpp install, and the clipboard tool
for `hyperframes add`, run by the absolute path the trusted lookup
approved. The media-use engine gets a PATH holding only trusted folders.

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

* fix(engine): fail a missing FFmpeg the way a failed spawn always has

Throwing from getFfmpegBinary turned every caller's missing-binary path
into a synchronous throw: the streaming encoder's "failure result, not a
throw" contract broke, and unit lanes that run without FFmpeg crashed at
module load. With no trusted copy the getters now return an absolute path
inside HyperFrames' own install that is never created, named for the
override to set. Spawning it fails with ENOENT exactly as before, and the
OS still never looks the bare name up. The call-site guards and fixture
changes that the throw needed are reverted.

The whisper install tests match git and cmake by name and skip the brew
case on Windows, where the lookup walks the real PATH.

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

* test(engine): pin the found FFmpeg before the HDR test looks it up as macOS on Windows

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-11 09:46:52 +00:00