Fix Chrome & Chromedriver installation using Chrome for Testing#14
Merged
Fix Chrome & Chromedriver installation using Chrome for Testing#14
Conversation
Fix chromedriver download fallback when exact version is unavailable
83ff638 to
e48a490
Compare
22a3d08 to
da355cb
Compare
gnulinooks
reviewed
Mar 25, 2026
7d83481 to
4a277c0
Compare
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
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
Chrome for Testing does not publish a chromedriver binary for every Chrome release. When the installed Chrome version (e.g.
146.0.7680.164) has no matching chromedriver at the exact URL, thewgetcommand fails and the action errors out.https://github.com/QuickPay/manager/actions/runs/23494135067/job/68371526465
Solution
Replace the old approach with a single fetch from the Chrome for Testing API: