Hello ChromeDriver users,
Until now, ChromeDriver had its own release process, separate from the Chrome release process. We’ll continue to follow this process for the M114 release later this month.
After the M114 release, we’re making some changes to fully integrate ChromeDriver into the Chrome release process. Starting with M115, 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.
Here’s what will be changing as of M115:
We’ll no longer provide manually curated release notes.
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.
We’ll no longer update the ChromeDriver website for every release.
Instead, consult the Chrome for Testing availability dashboard to view the latest Chrome + ChromeDriver releases per release channel (Stable, Beta, Dev, Canary).
We’ll no longer announce new releases via this email group.
Instead, consult the Chrome for Testing availability dashboard to view the latest Chrome + ChromeDriver releases per release channel (Stable, Beta, Dev, Canary).
Please let us know if the dashboard and its JSON APIs aren’t sufficient for you to stay informed on new releases.
The download location for ChromeDriver releases will change.
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 won’t publish new downloads to these locations in the future.
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 will significantly simplify the status quo, solving a number of issues:
It completely eliminates the manual ChromeDriver release process.
It aligns ChromeDriver releases with Chrome releases.
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
--
You received this message because you are subscribed to the Google Groups "ChromeDriver Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedriver-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/e295a5aa-796d-4840-afa4-031cc72720can%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "ChromeDriver Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedriver-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/CADizRgYQY55wwk9AoAYXe_O8_EcSEWm19VqPLsPo9oW9TSa8Cw%40mail.gmail.com.
Dear all,It is not so clear for me as I'm not a total expert on the use of chrome driver.However, I have developped a program for my organization that checks the chrome version and downloads automatically the right corresponding chrome driver version in case of change.Does this change mean that each time chrome will be updated, the chrome driver will be automatically installed at the same time and the same place ? Or do we still have to download chrome driver automatically from the new end point ?
Also do the naming of the different versions will follow the same rules as previously ?
Finally, do you know when the release of the chrome version 115 will be done ?
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/CAE68PjeW2v5xW7rfpD4L7D%3DohMYMV1X11G%3DTSHoAbihvD5A_Kg%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "ChromeDriver Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedriver-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/b4993503-692f-4558-a108-6ffecfa8814en%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "ChromeDriver Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedriver-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/1be3a95c-45d4-479c-86dd-b35e43907121n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/90b77dde-967a-4709-bc49-d480800e1cben%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/d1f0e6a3-6885-45eb-afe7-647010003debn%40googlegroups.com.
Hi,Is there a way for an automation to learn which version (or download URI) of chromedriver is the current stable? The JSON only lists all of the available versions, but it doesn't tell which one is the current one.Previous API was able to give compatible chromedriver version and it's download URI if I had chrome version.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/c838f79e-87d9-46ed-88b3-c3199f1df52fn%40googlegroups.com.
What are the differences between Actual Chrome release and chrome-for-testing. Is something not included or optimized for automation performance. Is this mentioned in any blog or something.
How can I ensure that automation using chrome-for-testing is enough to replicate the real cases by users using actual chrome?
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/17b701f4-f4a9-41f9-886c-cb64139d2985n%40googlegroups.com.
Hello Mathias,I downloaded the chromedriver for mac-arm64. It is still throwing chrome binary errorcan you please help
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/a7794518-748a-4e67-aea7-329de412e382n%40googlegroups.com.
Are there plans to add .deb files for at least the google chrome download?
Also worth noting, but the chrome-linux64.zip does not include the google-chrome executable. So perhaps it wouldn't have worked anyways?
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/609eae16-d65d-4e07-891f-11c42d7e27f6n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/0d6a5134-bb87-4d5b-84d7-9592f484f7f2n%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "ChromeDriver Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedriver-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/b5ad12d0-df80-4457-8104-1082f3d85ea8n%40googlegroups.com.