Re: [chromium-dev] Impact of the new 2-week release schedule on downstream fork integration

[Marshall Greenblatt]

(moving chromium-dev to BCC, adding embedder-dev to CC).

Thank you for raising this issue. Given the long tail of most release processes, I would hope that the majority of websites allowlist versions by time frame (e.g. anything released in the past 3 months). For Chromium embedders specifically, I don't think the majority will adopt a two week release cycle. For example, I've outlined CEF's options at https://github.com/chromiumembedded/cef/issues/4114.

On Wed, Mar 4, 2026 at 9:11 AM Gediminas Veiverys <g.vei...@gmail.com> wrote:

https://developer.chrome.com/blog/chrome-two-week-release

The two week release schedule potentially adds more strain to the integration and release cycle for chromium fork maintainers. I think is is true even with the extended stable cycle remaining unchanged.

1. Browser detection javascript run by many websites in many forms is going to be less forgiving as they rely on version checks at least in part. This is also something that is not going to be adjusted any time soon in a general sense, given the wide variety of implementations each site may run.

2. Captcha services will likely flag more often. These may be concentrated to a few big services and rely on a lot more data than just client version string, but they are difficult to address on the client side whey they do happen and I think more false positives can happen.

Other than matching the 2x release cycle speed increase, what's your comment or recommendation going forward to mitigate these potential problems?

Let's say (1) could be in theory addressed by adding to UA-CH
https://developer.mozilla.org/en-US/docs/Web/API/User-Agent_Client_Hints_API use cases.

<...>

* Blocking spammers, bots, and crawlers.

* New: Improving false positives rate for bot detection

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/607d9a3e-11c9-4079-a2df-721994e82eben%40chromium.org.