search

GoogleChromeLabs / chrome-for-testing

https://googlechromelabs.github.io/chrome-for-testing/
Apache License 2.0
639 stars 71 forks source link

Early Stable Releases #71

Open titusfortner opened 10 months ago

titusfortner commented 10 months ago

I'm looking to programmatically get the early stable versions when they are released to dynamically update the pdls in the Selenium repo. I want to get Selenium releases out before production chrome is released to minimize warnings in people's logs.

For https://googlechromelabs.github.io/chrome-for-testing/last-known-good-versions.json Will the stable version get updated only after the official stable release? Or can we get an EarlyStable tag in that file when it is appropriate?

I can do it manually if needed, just trying to automate more things in our build/release cycle. Thanks.

titusfortner commented 10 months ago

Related, is Stable Release going to be delayed this time since Early Stable Release isn't released, yet?

mathiasbynens commented 10 months ago

I want to get Selenium releases out before production chrome is released to minimize warnings in people's logs.

The mechanism to use for this is the CfT release corresponding to the Canary channel (or Dev or Beta depending on how close to Stable you want to be).

CfT is designed to match the Chrome release schedule. In general, a CfT release only gets published whenever the corresponding Chrome release happens, not before. W.r.t. Early Stable Releases of Chrome, I don’t know exactly how the release process is handled — I’ll ask a Release Manager.

mathiasbynens commented 10 months ago

W.r.t. Early Stable Releases of Chrome, I don’t know exactly how the release process is handled — I’ll ask a Release Manager.

Early Stable Releases go out to a small number of users, and only on Windows and macOS (not Linux), so there wouldn’t be a corresponding CfT release for such versions at that point.

titusfortner commented 10 months ago

In the past, Early Stable Release versions have showed up here: https://chromereleases.googleblog.com/ There wasn't one last week for 119 on the day expected (a new beta was released instead)...

To ensure a good experience for Selenium users, I want to generate CDP classes on the early stable release and have a new Selenium version ready for users when stable release happens. Now that CfT exists, I'm expecting people are going to be updating their versions earlier by default.

It makes sense that isn't automated via CfT, though; I can do it manually, but I guess there won't always be an announcement?