xcode-install VS semver

If you don't want to have a UI and instead prefer cli go for https://github.com/xcpretty/xcode-install

xcode-install is a handy tool to automate some steps managing installs. You can keep using versions while downloading others.

you should be able to deploy a script inspired by this I haven’t try it just an idea.

I downgraded Xcode to 12.4. But you can use https://github.com/xcpretty/xcode-install it enables you to change in your terminal the version of xcode you use.

I use xcversion https://github.com/xcpretty/xcode-install

But I also use tags whenever I plan to start on a major revision (using the Semantic Versioning 2.0 style https://semver.org to the best that I can). That way I can reset to it if something terribly goes wrong, or if I end up abandoning the change.

https://semver.org/ is pretty great for most things.

Just follow the rules for semantic versioning and you will be fine https://semver.org/

Tags of the form MAJOR.MINOR.PATCH (such as 3.17.2) indicate the Semantic Version of the Alpine image used as the base.

Big under-the-hood changes. Nintendo seem to use Semantic versioning with Horizon (switch OS) version numbers. The short meaning is that a lots of stuff getting refactored and changed internally means the major version gets bumped (15 -> 16), despite little in the way of frontend customer-facing changes.

Err... that's no way to judge the success of a software project. If you are properly following the semantic versioning spec (which they appear to be), then there's no need to bump the major version if the API is backwards compatible. When working in very complex systems, bumping majors is often worse than making your changes backwards compatible. Loads of very successful projects go years without bumping a single major version.

From https://semver.org Note this as above explained not the case in Rust