Announcement: the new ChromeDriver release process is live!

[Mathias Bynens]

Hello ChromeDriver users,

Until now, ChromeDriver had its own release process, separate from the Chrome release process.

As of M115, we’re happy to announce that ChromeDriver is fully integrated into the Chrome release process. Across all release channels (Stable, Beta, Dev, Canary), every Chrome release that gets pushed to users automatically gets a correspondingly-versioned ChromeDriver release, available for download via Chrome for Testing infrastructure.

As announced previously, here’s what’s changing as of M115:

1. We no longer provide manually curated release notes.

1. Instead, view the commit history in your local Chromium checkout via git log chromium/src/chrome/test/chromedriver or online via https://github.com/chromium/chromium/commits/main/chrome/test/chromedriver.

2. We no longer update the ChromeDriver website for every release.

1. Instead, consult the Chrome for Testing availability dashboard to view the latest Chrome + ChromeDriver releases per release channel (Stable, Beta, Dev, Canary).

3. We no longer announce new releases via this email group.

1. Instead, consult the Chrome for Testing availability dashboard to view the latest Chrome + ChromeDriver releases per release channel (Stable, Beta, Dev, Canary).

4. The download location for ChromeDriver releases is changing.

1. This applies to both the old ChromeDriver Stable + Beta downloads at https://chromedriver.storage.googleapis.com/ as well as the old Canary downloads at https://chromedriver.chromium.org/chromedriver-canary. We’ll stop publishing new downloads to these locations in the future.

2. Consult the Chrome for Testing availability dashboard to learn about the new URL format. Use @puppeteer/browsers to easily download and launch browser + driver binaries, or build your own custom solution using our JSON API endpoints.

We believe the new, automated, and aligned release process significantly simplifies the status quo & solves a number of issues:

1. It completely eliminates the manual ChromeDriver release process.

2. It aligns ChromeDriver releases with Chrome releases.

3. It makes it significantly easier for users to download matching Chrome for Testing + ChromeDriver binaries.

Thanks for your continued support of ChromeDriver, and please let us know if you have any questions.

Sincerely,

The ChromeDriver Team