CI Worflows: point the Chrome mismatch strings to secrets #8721
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.
Discussion
We have some debug warnings if the latest installed Chrome verison doesn't match the latest vetted Chrome version for Auth Tests. This change was originally made due the Chrome version causing certain Auth tests to fail, but determining the issue was due to a Chrome version change was cumbeersome and a second thought.
This change pushes the configuration of
CHROME_VALIDATED_VERSION
out of the CI workflow and into our GitHub secrets. This should let us update the value easier as it wouldn't require a PR.Testing
CI
API Changes
None.