Hi,

We have officially branched to be prepared for the upcoming Chrome version
*144*.
The base of the branch is currently rolled into Chromium. It is based on
the latest V8 version.

Integration into Chromium is stopped until Chromium has branched too.

V8 branch: *branch-heads/14.4*
V8 Version: *14.4.258*

If your CL is not included in *14.4.258* you might consider merging it into
the branch
*branch-heads/14.4*. In that case please apply the label *Merge-Request-144*
to the bug
the CL is fixing. See https://v8.dev/docs/merge-patch for more information
on merging.

Thanks,
Jakob

On Fri, Nov 28, 2025 at 4:36 PM Jakob Kummerow <[email protected]>
wrote:

> Hi,
>
> It is time again. If you have any questions regarding the release, please
> ping this thread.
>
> FRIDAY 2025-11-28: API adoption freeze starts.
>
> V8 will branch on MONDAY for the upcoming Beta phase for Chrome 144.
>
> In order to make this synchronization as painless as possible for V8 and
> Blink, please don't make API changes which make the revert more difficult
> and don't adopt API changes. When in doubt, ask vahl@.
>
> MONDAY 2025-12-01: Create 14.4 branch
>
> based on one of the latest V8 versions. The auto-roller is closed. Keep in
> mind that this means we are not integrating with Chromium (much less test
> coverage). If you happen to work on an important fix, please make sure that
> the fix is on 14.4 too! See information on merging & patching for the
> details.
>
> Latest TUESDAY 2025-12-02: Back to normal and API adoption freeze is
> lifted.
>
> Auto-roller is running again and we are back to normal business.
>
>
>

-- 
-- 
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
--- 
You received this message because you are subscribed to the Google Groups 
"v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/v8-dev/CAKSzg3SC-WQWi%2B-YO_ZUeHQH9B5GCt%2B0WZWOiJ2WNWy%3DihFeQQ%40mail.gmail.com.

Reply via email to