I don&#x27;t think the issue here is that it requires work to upgrade across multiple major versions. Rather, it is that &quot;two major versions back&quot; is only about 1.5 years ago, and that major building blocks got abandoned in the mean time.<p>If you have projects that do not see any updates for a few years (fairly common, in my experience), then see urgent requests come in (in this example, it was that a Chrome update broke the app, but it might also be a feature request. Normally, those shouldn&#x27;t require upgrading technology to new versions, but there may be security fixes that didn&#x27;t get backported, or it may no longer be feasible to get people who know how to use that &#x27;ancient&#x27; version), that can get annoying fast.<p>Lesson learned should be that one should not blindly use the latest, shiniest, technologies, but take longevity of the product into account. Problem for web-based stuff is that there is not really a stable product that one can count on to be around mostly unchanged in a few years time, and that is best in class or at least close to it. Evolution is just too rapid.