Best practice on project versioning

[jmarq013]

Hi folks 👋 I'm wondering what the best way to manage the CURRENT_PROJECT_VERSION and MARKETING_VERSION build settings when adopting Tuist.

I'd like to be able to hold the source of truth of the version in some kind of .txt / .plist file and have the manifest files read it and propagate those version settings to the project / target plist files. Is there some built-in way / API for achieving that if I kept the version number file at the root of the project?

FWIW, I would like to be able to set/increment these version numbers from CI - hence the usage of .txt / .plist files.

Thanks in advance!

[Ernest0-Production]

I think a more correct solution for working with non-generated settings is to use xcconfig and update the version in this file.
Fastlane has a plugin that allows you to do this conveniently.

As far as I know, the tuist documentation also recommends keeping all user settings in xcconfig, but I think it's more about managed values, not custom-default ones.

[jmarq013]

Thanks so much! Yeah, that feels like it's more in-line with the idea of keeping all settings in xcconfig files 💯 Great call on the Fastlane plugin, too (found it)! I think holding the source of truth in the xcconfig file is a lot cleaner