&gt;
... but going to v4 in one year isn&#x27;t as unstable as it sounds; it&#x27;s just following Chrome&#x27;s example of not caring how big the version number gets, so long as the semantics make sense.<p>Except that Chrome is mainly an application for end users and not a library, so the implications of &quot;breaking changes&quot; are a lot less severe anyway.
In the parts where it does provide APIs (e.g. to websites or add-ons), the compatibility policies are a lot stricter than semver would require.