From 6bfefa53da24ccbf703ea8f22380e60f718aa107 Mon Sep 17 00:00:00 2001 From: Tim van der Meij Date: Sun, 14 Jun 2026 16:28:36 +0200 Subject: [PATCH] Configure Puppeteer to use the stable version of Chrome We currently use the pinned version of Chrome as hardcoded in the Puppeteer release, which is based on the version of Chrome that was deemed stable at the time of the Puppeteer release. However, this is not ideal because it means that Chrome updates are strongly tied to Puppeteer releases, so if Puppeteer releases are slow we could be missing out on e.g. (security) patches being applied on the stable channel. It's also not consistent with Firefox where we don't use a hardcoded pinned version either. This commit therefore configures Puppeteer to use (resolve) the most recent stable version of Chrome at the time of the installation so that determining the browser version to use is fully decoupled from the Puppeteer release we're running. The effect of this change can be seen in the output of running `npx puppeteer browsers list`: Before: `chrome@149.0.7827.22 (linux) ` After (note the slightly newer version): `chrome@149.0.7827.115 (linux)` ` --- .puppeteerrc.json | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.puppeteerrc.json b/.puppeteerrc.json index d45a2f2fd..4401066f6 100644 --- a/.puppeteerrc.json +++ b/.puppeteerrc.json @@ -1,6 +1,7 @@ { "chrome": { - "skipDownload": false + "skipDownload": false, + "version": "stable" }, "chrome-headless-shell": { "skipDownload": true