In my (too long) experience of C and C++ this is absolutely not the case. New compiler versions are much more frequent than new language standards and frequentl

In my (too long) experience of C and C++ this is absolutely not the case. New compiler versions are much more frequent than new language standards and frequently will barf on existing code when you make an upgrade. Usually when it happens it will be because of some unsafe/undefined/broken edge case that noone thought of before so some (evil) developer relied on it and then the subsequent compiler writer figured out how to detect and warn/error on. The whole premise of the article seems weird to me. "New compiler detects problem in old code" doesn't seem like a bug to me especially if the breakage is caused by type inference. If you want the ci/cd to not change in any way then you need to build in an environment which doesn't update in any way.