It's WWDC time of the year, betas of new Apple technology have landed.

Just as I finished writing previous rant about how Apple claims to have dropped support for old system, while they actually haven't, the situation has somewhat changed - not only minimum deployment targets (Apple terminology for operating system version required by the built program) have been raised again, but compiling programs for operating systems older than documented minimum deployment target now actually fails.
This isn't the first time Apple tried to axe support for these operating systems - Xcode 15 already required special workarounds because C++ programs built with default settings just crashed below macOS 12 / iOS 15, see Xcode 15 release notes, search for ld_classic, the recommended workaround was to to drop support for affected operating systems at the time already. Apple fixed/reverted this shortly after.

Anyway, let's focus on macOS side for now.

foobar2000 currently requires macOS 11.
I'm not particularly fond of macOS 11 release in any way, but it did introduce useful features (SF Symbols), and it's the newest operating system I can legitimately install on my only Intel Mac.
It's a convenient setup for me - if new code works on development system running latest macOS and Intel Mac running macOS 11, everything inbetween is most likely OK too.
Here are the options I could think of right away:
1) Get macOS 12 or newer running on the Intel Mac, using available patching tools.
2) Run virtual machines with newer macOS on the Intel Mac.
3) Buy a newer Intel Mac (ha ha good one).
4) Drop support for affected systems in develoment branch (so I can debug it with new Xcode), compile release branch via xcodebuild from old Xcode.app. Tedious, but works.
5) ... or just postpone updating macOS & Xcode on the development system for as long as I care about Intel & macOS 11.
From all of these, 5) sounds like the route of least pain to me, with fallback to 4).

The future?

I'm certainly not raising macOS system requirements this year.
Much depends on whether the Xcode 27 beta behavior stays or gets reverted like it happened with Xcode 15.