On Sun, Oct 22, 2023 at 11:32 AM Meir Shpilraien <[email protected]> wrote:
>
> Hey,
>
> According to the documentation, around every 4 weeks a new stable version is 
> tagged and the maintenance of the previous version is stopped. This is why we 
> should make sure we are always up to date with the latest stable version:
>
> https://v8.dev/docs/release-process#which-version-should-i-embed-in-my-application%3F
>
> That said, I saw that chromeOS has a long term support version which is 
> released every six month. Assuming I take the V8 version which ship with this 
> LTS version of chromeOS, can I assume that I will get patches on this V8 
> version on critical bugs and security fixes?
>
> I am asking because I want to understand my options about upgrade 
> requirements.
>
> Thanks,
> Meir.

Another option is to track Node.js's "fork" of V8. We maintain our
copy in deps/v8 for as long as the corresponding node release branch
is maintained. E.g. the v20 branch gets support until April 2026.

Caveat emptor w.r.t. security fixes: node's threat model differs from
chromium in that executed code = trusted code. Local exploits are not
prio-drop-everything like they are for chromium.

-- 
-- 
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 on the web visit 
https://groups.google.com/d/msgid/v8-dev/CAHQurc_kRdMT5atAb6iNp_zV%2B5Vgx1FGu9JGYvdagqHjWWzZvQ%40mail.gmail.com.

Reply via email to