Either upload beta chromedriver versions ahead of time, or build an automated way to update the version

[sglajchEG]

For instance, today chrome went from v101 to v102, and the 102 artifact wasn't here. So we have to notice our broken builds, do an emergency PR here, and then move to the v102. However v103 is already up on chrome already. If we uploaded both the 102 (stable) and 103 (beta) versions, then the versions would exist ahead of time, and chrome go-live day for the next major version won't be such a fire drill.

Alternatively, some process might be developed to do this automatically, though I understand that this maybe a harder task.

[clicman]

Hi! your alternative sounds better, I will think about it in few days and back

[clicman]

The main point is to find free node for watchdog process, or maybe lamda function will enough for it

[ispringer]

An automatic updater would be awesome. A Lambda on a schedule sounds like a great fit.

In the meantime, I'll open a PR for v103 now.