- 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>
* fix(ci): a release fails its checks when its notes miss a commit merged after the cut
* fix(ci): shorten the release checks comment
* fix(ci): find the last release by subject and say to link a deliberate omission
* ci: a release PR runs a fast release check, not the heavy suites
* ci: keep the release check's header within the comment limit
* ci: shorten the release check's usage line
* ci: trim the release check's comments
* ci: the release check's classifier hands the manifest test to a helper