If it ain’t broke, …

However, if you’ve set-up PATH yourself, as the OP had, you’re on your own, I’m afraid!

I wonder if that was documented.

At a previous job, I found a segfault when I used a newer version of the compiler we use (GCC) on our codebase. The root cause was invoking undefined behavior in some C++ code that just happened to work with the existing compilers (GCC and the Solaris C compiler). My manager (who introduced the bug) refused to fix it unless I wrote a test case (impossible as the existing compilers produced working code) or come up with a way to detect all occurrences of said issue (I think that would be a Ph.D.-style research topic, if possible at all). I think my manager was afraid to do more than the bare possible minimum (new manager---was probably treating the code base as "legacy", whereas I had been working on it since it started, and it had test cases) and wanted minimum changes as possible to avoid production disruptions. But the fix itself was trivial---just moving two lines of code. Technically, it wasn't broken. For now. Later though?

The problem with not fixing warnings from your tooling is that they build up, and at some point it's hard to recognize which are the warnings that have been there for 5 years and are harmless, and which is the new warning that you just introduced while making a change and is going to make your whole day bad.

I don't really know how to thread that needle except to fix warnings! Dunno, there must be a better way, but I don't know it.