Skip to content

Fork patch: Cloud Run image on the CLI's Chrome (152) - #3

Closed
valeriangalliat wants to merge 1 commit into
mainfrom
patch/cloud-run-chrome-152
Closed

valeriangalliat wants to merge 1 commit into
mainfrom
patch/cloud-run-chrome-152

Conversation

@valeriangalliat

@valeriangalliat valeriangalliat commented Oct 6, 2026 •

Copy link
Copy Markdown
Collaborator

🤖 AI agent: Arcade fork patch. Do not merge.

This draft shows patch/cloud-run-chrome-152 against main, the upstream mirror, so the patch has one page for its diff, its revisions and its reason. Arcade's /hyperframes-update rebases the branch onto main and cherry-picks it onto arcade; this PR is not part of that flow. When a rebuild changes the patch, its git range-diff against the previous sync/<date>/cloud-run-chrome-152 tag is posted as a comment.

Why

packages/gcp-cloud-run/Dockerfile pinned chrome-headless-shell 148.0.7778.167, while the CLI manages 152.0.7977.30 (packages/cli/src/browser/manager.ts). Chrome 148 leaves descendants with their own paint layer (transform, filter, opacity, position, will-change) out of a background-clip: text clip. A split-text gradient line therefore renders invisible on Cloud Run while local renders and previews show it. 150+ paints it. Pinning Cloud Run to the CLI's build makes both produce the same frames.

Repro: patch/bg-clip-text-layered-child.

Upstream

Issue #5117: gcp-cloud-run and Dockerfile.test still pin 148 on upstream main. Maintainer fix #5338 moves both images to 152 and adds a regression fixture; open as of 2026-10-24.

Drop when

Upstream moves the Cloud Run pin to 150 or later.

Arcade

ARC-15991 · corpus scene gradient-text-split-lines · ArcadeHQ/arcade#11396

…s managed build

148 leaves layered descendants (transform, filter, opacity, position,
will-change) out of a background-clip: text clip, so split-text gradient
lines render invisible. 150+ paints them. Matching the CLI pin
(packages/cli/src/browser/manager.ts) makes local render and Cloud Run
produce the same frames.
@valeriangalliat
valeriangalliat force-pushed the patch/cloud-run-chrome-152 branch from 1f58ef5 to 196c951 Compare October 24, 2026 23:23
@valeriangalliat

Copy link
Copy Markdown
Collaborator Author

🤖 AI agent: sync/2026-10-24: rebased onto upstream 722481214 (0.8.193). Context only: upstream rewrote the lines above the pin. Still needed: upstream main still pins 148; heygen-com#5338 moves it to 152 and is open.

git range-diff sync/2026-10-05/base..sync/2026-10-05/cloud-run-chrome-152 sync/2026-10-24/base..sync/2026-10-24/cloud-run-chrome-152
1:  1f58ef58b ! 1:  196c951ea fix(gcp-cloud-run): pin chrome-headless-shell 152.0.7977.30, the CLI's managed build
    @@ Commit message
         produce the same frames.
     
      ## packages/gcp-cloud-run/Dockerfile ##
    -@@ packages/gcp-cloud-run/Dockerfile: RUN apt-get update && apt-get install -y --no-install-recommends \
    +@@ packages/gcp-cloud-run/Dockerfile: RUN case "$TARGETARCH" in \
      # Pinned deliberately. The build-stage contract probe below launches this
      # exact executable and requires a renderer-ready warm-up plus a PNG-returning
      # HeadlessExperimental.beginFrame before the image can build.

@valeriangalliat

Copy link
Copy Markdown
Collaborator Author

🤖 AI agent: Dropped on sync/2026-10-24 (upstream 2e397dba5, v0.8.194). Upstream #5338 pins chrome-headless-shell@152.0.7977.30 in packages/gcp-cloud-run/Dockerfile, the same line as this patch, and closed #5117. The patch rebased to empty. History stays on the sync/<date>/cloud-run-chrome-152 tags (last: sync/2026-10-24/cloud-run-chrome-152, on 0.8.193).

@valeriangalliat
valeriangalliat deleted the patch/cloud-run-chrome-152 branch October 25, 2026 02:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant