[rust] Download older and unstable version of Chrome for Testing (#11678) #12410
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.
Description
This PR implements the Rust logic required to manage Chrome for Testing (CfT) binaries: unstable channels (beta/dev/canary) and fixed versions (e.g., 113, 114, 115, etc.).
Here it is some examples of its usage:
Chrome stable (forced download)
Chrome beta (already installed)
Chrome dev (not available, and so, CfT is downloaded)
Chrome 113 (not available, and so, CfT is downloaded)
Motivation and Context
This PR is a continuation of #12353 and implements #11678. It allows to download CfT browser binaries, starting on Chrome 113 (the first version released as CfT).
Now, we need to decide if we want to support the management of even older Chromium releases (e.g., 112, 111, etc.). This could be done by mapping these releases (using the info published in the Chromium Dash).
@diemol @titusfortner Do we want to manage these Chromium versions (i.e., older than 113)? It is feasible. In fact, this was the original idea before releasing CfT.
Types of changes
Checklist