- Issue created by @mstrelan
- 🇬🇧United Kingdom catch
I think we might want to pin this permanently and then update each chrome release, or find a way to run on latest in the updated deps job.
- Status changed to RTBC
3 months ago 11:57pm 29 August 2024 - 🇬🇧United Kingdom catch
I had to rerun the 128 branch to see some functional js test failures, but then there were two, so does indeed look like those are more frequent.
Going to go ahead and commit here, we'll need a follow-up to update to chrome 128 properly, and then we can decide whether to pin or go back to latest then.
- Status changed to Fixed
3 months ago 12:15am 30 August 2024 - 🇬🇧United Kingdom catch
Committed/pushed to 11.x, thanks! Opened 📌 Update to selenium/standalone-chrome:128 Active .
Automatically closed - issue fixed for 2 weeks with no activity.