Fix #736 legacy ChromeDriver downloads for Chrome 114 and older#737
Merged
aleksandr-kotlyar merged 5 commits intoJun 4, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
webdriver-manager 4.1.1 can build invalid ChromeDriver URLs for older Chrome versions, e.g. ChromeDriver 102 on Windows:
https://storage.googleapis.com/chrome-for-testing-public//102.0.5005.61/chromedriver_win64.zipChromeDriver 114 and older still use the legacy
chromedriver.storage.googleapis.comflow, while Chrome for Testing applies from M115.Solution
win64to the legacywin32archive name for pre-115 ChromeDriver.Tests
ChromeDriverManager.install()without live network calls.