[5.5] Improve detection of latest stable ChromeDriver release #677
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.
By default,
php artisan dusk:chrome-driver
downloads the latest stable ChromeDriver release. We are currently parsing http://chromedriver.chromium.org to get the version number, but that's not ideal. When the HTML changes (as it did last week), it breaks the updater (#672).https://chromedriver.storage.googleapis.com/LATEST_RELEASE does contain this version number, but the file had been deprecated for the last months. I explained our issue to the ChromeDriver team and they removed the deprecation: https://bugs.chromium.org/p/chromedriver/issues/detail?id=3128