API stability

mi-ac edited this page Nov 22, 2016 · 1 revision
Clone this wiki locally

If V8 in a Chromium canary turns out to be crashy, it will get rolled back to the V8 version of the previous canary. It is therefore important to keep V8's API compatible from one canary version to the next.

We continuously run a bot that signals API stability violations. It compiles Chromium's HEAD with V8's current canary version.

Failures of this bot are currently only FYI and no action is required. The blame list can be used to easily identify dependent CLs in case of a rollback.

If you break this bot, be reminded to increase the window between a V8 change and a dependent Chromium change next time.