Agent skill · software engineering · remotion-dev
update-chrome-binaries-test-region
Publish Remotion Lambda Chrome binaries to the eu-central-1 test region and update hosted layer and Chrome version references. Use when updating Chrome binaries before full regional rollout.
Why this skill is useful
Adds a detailed automation script for publishing and updating Chrome binaries in AWS Lambda, including specific commands and verification steps that are not commonly known.
What it needs
Requires aws-cli, bun, docker installed locally. Requires aws account access. About 3k tokens when loaded. Last updated 2026-08-06. 55,698 stars on the source repository.
What this skill does
Update Chrome Binaries Test Region AWS setup Confirm the AWS CLI is logged into account 678892195805 by running aws sts get-caller-identity. If not, ask the user to log in. Export AWS credentials into the shell by running eval "$(aws configure export-credentials --format env)". The Lambda client checks for AWSACCESSKEYID and does not pick up SSO or Identity Center credentials on its own. From packages/lambda, run bun src/admin/make-layer-public.ts --region=eu-central-1 to publish all 5 layers: fonts, chromium, emoji-apple, emoji-google, cjk. The eval and the bun command must run in the same shell invocation because the env vars do not persist across shell calls. Verify the output prints a LayerArn and Version for each of the 5 layers and a final JSON dump with the published regions populated. Update hosted layers Update packages/lambda/src/shared/hosted-layers.ts by copying the JSON dump from the script's stdout. Do not manually bump version numbers. The script prints, after several blank lines, a complete HostedLayers object showing the exact layerArn and version AWS returned for every layer it just published. Replace the corresponding region entries in hosted-layers.ts with those values. For the test phase (--region=eu-central-1), only eu-central-1 is updated; other regions intentionally stay on their old versions until rollout. If the script was invoked with --skip=<region>, leave skipped regions untouched. Update Chrome references Use the Chrome version supplied by the user, such as 157.0.8080.0. Default downloads no longer use a Playwright revision. Verify the same Chrome version is available for all supported platforms in Google's Chrome for Testing download metadata. If an exact match is unavailable, choose the closest available version and keep its version/cache marker accurate. Explicit numeric Playwright revision overrides on Linux ARM64 remain supported. Update: packages/renderer/src/browser/get-chrome-download-url.ts: TESTEDVERSION. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills remotion-dev/update-chrome-binaries-test-region