[user-github-me]

The Kubernetes distributed-renderer example still installs Chrome 148, which has the layered gradient-text defect addressed in #5338. Update it to 152.0.7977.30, matching the managed Linux browser and Cloud Run image.

This is the K8s follow-up accepted in review 5640641289.

Validation:

• Verified the one-line pin change, version agreement, normal commit hooks and both comment checks.
• Built the exact Dockerfile prefix through Chrome installation for Linux/amd64. Its installed Chrome 152 binary launched and passed the existing BeginFrame capture probe.
• The complete example build passed system dependencies, FFmpeg verification and Chrome installation, then stopped at an existing ffmpeg-static download timeout during bun install. The complete image and current renderer remain unverified.

[miguel-heygen]

Thanks for catching this. The new pin matches the managed Chrome build exactly: CHROME_VERSION in packages/engine/src/services/chromeHostCeiling.ts:26 is 152.0.7977.30, and the Cloud Run Dockerfile:83 and Dockerfile.test:83 already install that version. #5338 moved those two from 148.0.7778.167 but missed this example, even though its comment at Dockerfile.example:110 says it follows the Cloud Run pin, so the old value was stale. PRODUCER_HEADLESS_SHELL_PATH is built from the same variable, so the install path follows the change, and no other reference to the old build remains.

Optional, not for this PR: a small check that compares these container pins with CHROME_VERSION would catch the next drift automatically.

Verdict: APPROVE
Reasoning: One-line pin now equals the repo's managed Chrome version and the Cloud Run pin, fixing a drift left by #5338; CI is green with path-filtered skips.