Replies: 1 comment
-
Hey @reshadf 👋 In the company I work at, we've concluded that it's much easier and safer to explicitly pass the version being released as an argument when deploying. The reason is that you are the person who knows the best which version should be the next version to be released, i.e. whether it's gonna be a patch release, a minor, or a major release. Our build number is automatically during build phase (it's an auto generated number that has guaranteed uniqueness), so we don't have to manually bump it upon releasing.
This can be achieved by using spaceship's available functions, you can call them directly from ruby/Fastfile, if you think it better fits your needs 😊 Hope this other point of view help you out 🙌 |
Beta Was this translation helpful? Give feedback.
-
so we have been trying to implement increment_version_number and increment_build_number via Fastlane. However, there are so many implementations that there is no clear way of "automating" This results in a big team of devs to always commit the "marketing version" manually before starting a new release or use some other script/tool to do this.
I was thinking, why do we not get the current released version from the app store in order to update this?
Beta Was this translation helpful? Give feedback.
All reactions