Branch cut V8 13.3 on 2025-01-03

28 views
Skip to first unread message

Michael Achenbach

unread,
Jan 2, 2025, 5:53:14 AMJan 2
to v8-...@googlegroups.com

Hi,

It is time again. If you have any questions regarding the release, please ping this thread.

THURSDAY 2025-01-02: API adoption freeze starts.

V8 will branch on FRIDAY for the upcoming Beta phase for Chrome 133.

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 machenbach@.

FRIDAY 2025-01-03: Create 13.3 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 13.3 too! See information on merging & patching for the details.

Latest 2025-01-08: Back to normal and API adoption freeze is lifted

Auto-roller is running again and we are back to normal business.

Michael Achenbach

unread,
Jan 3, 2025, 5:41:17 AMJan 3
to v8-...@googlegroups.com
Hi,

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

Integration into Chromium is stopped until Chromium has branched too.

V8 branch: refs/branch-heads/13.3
V8 Version: 13.3.415

If your CL is not included in 13.3.415 you might consider merging it into
the branch refs/branch-heads/13.3. In that case please set the Merge-Request
field to 133 on the bug the CL is fixing. See https://v8.dev/docs/merge-patch
for more information on merging.

Thanks,
Michael
--

Michael Achenbach | Software Engineer, V8 | Google Germany GmbH | Erika-Mann-Str. 33, 80636 München 

Registergericht und -nummer: Hamburg, HRB 86891 | Sitz der Gesellschaft: Hamburg | Geschäftsführer: Paul Manicle, Liana Sebastian 
Reply all
Reply to author
Forward
0 new messages