In Xcode 14, I have left the deployment target at 10.11 and it still works. Tested on VMs and no user complaints. I’m guessing the danger is if I use a newer feature going forward I won’t get a warning / compile error then it will blow up on user machines.
In addition, developers that are protecting their products with PACE should check out the recent email from PACE whose subject starts with “Eden SDK 5.6.3, macOS Ventura”, for their stance about updating build enviroments to Ventura and Xcode14.
(sorry, can’t go into more details because of the agreement with PACE. Now that JUCE is part of PACE, it would be nice if there were a subsection of the forum only available to verified users of their SDK that have signed the NDA)
I finally upgraded my secondary laptop to Ventura and can confirm the workaround is possible. After upgrading the OS, just rename Xcode.app to Xcode13.app, install Xcode 14 and then launch Xcode13 using the terminal. /Applications/Xcode13.app/Contents/MacOS/Xcode
This leads to an “interesting” about dialog, and obviously shouldn’t be used for production builds, but otherwise it appears to work mostly fine (so far).
No surprise. Expect macOS 14 and xcode 15 to drop 10.13 and 10.14 (or 10 entirely?).
Now the real speculation is when they will drop OpenGL support and wreak more havoc.
We’ve been supporting 10.9.5 and higher for a long time now, and have no plans to stop, as there are SO many users running macOS versions earlier than 10.13. I wish Apple would slow down their rate of forced obsolescence.