Branch cut V8 14.5 on 2026-01-12

11 views

Skip to first unread message

Michael Achenbach

unread,

Jan 9, 2026, 5:53:12 AM (4 days ago) Jan 9

to v8-...@googlegroups.com

Hi,

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

FRIDAY 2026-01-09: API adoption freeze starts.

V8 will branch on MONDAY for the upcoming Beta phase for Chrome 145.

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

MONDAY 2026-01-12: Create 14.5 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.5 too! See information on merging & patching for the details.

Latest TUESDAY 2026-01-13: 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 12, 2026, 9:14:23 AM (yesterday) Jan 12

to v8-...@googlegroups.com

Hi,

We’ve officially branched to be prepared for the upcoming Chromium version 145. The base of the branch is currently rolled into Chromium. Integration into Chromium is stopped until Chromium has branched too.

V8 branch: refs/branch-heads/14.5

V8 Version: 14.5.201

If your CL is not included in 14.5.201 (log: https://chromium.googlesource.com/v8/v8/+/refs/branch-heads/14.5 ) you might consider merging it into the branch refs/branch-heads/14.5. In that case please set the Merge-Request field to 145 on the bug the CL is fixing. See https://v8.dev/docs/merge-patch for more information on merging.