#ReactNative developer interested in doing apps faster 🏎 and animated 🖼. Author of http://savee.io , react-native-material-ui and react-native-motion
There is no concurrency at all I think. Two commits can’t have the same version. If you merge PR to the master while there is a release happening it should (in the best case) stop doing the release and start doing the new release (that’s what you can set up on CI). But even if those releases happening parallelly, both of them will have a different…
Have you read my other article? https://blog.usejournal.com/semantic-release-for-fastlane-781df4cf5888
I believe you can find more code and also link to the Fastlane plugin (which is open-sourced on my GitHub account — https://github.com/xotahal
Hi Adam, not sure what exactly you want me to tell you :) If you are asking about how to setup alpha/beta/production for react native apps there is plenty of content on the web (at least I think). And you can be also inspired by a setup of native apps. For ios you will set up targets in xcode for android flavors in gradle.
You can do this by Gradle/Fastlane now. But I was always lazy to take care of versions, release notes, etc. So I’ve done everything automatically. With CI tool. By analyzing GIT commits.