- Start a git-flow release/x.y.z
- Create a CHANGELOG.latest.md with the changes for the current version (to be used by Fastlane for the github release notes)
- Update the version number by running
bundle exec fastlane bump_and_update_changelog version:x.y.z
- Commit the changes
git commit -am "Version x.y.z"
- Make a PR, merge when approved
cd bin
./release_version.sh -c x.y.z -n a.b.c
, where a.b.c will be the next release after this one. If you're releasing version 3.0.2, for example, this would be./release_version.sh -c 3.0.2 -n 3.1.0
. This will do all of the other steps in the manual process.- Make a PR for the snapshot bump, merge when approved
- Create a branch bump/x.y.z
- Update the version number in
RCPurchases.m
,Purchases.podspec
and inPurchases/Info.plist
by runningfastlane bump version:x.y.z
- Update CHANGELOG.md for the new release
- Commit the changes
git commit -am "Version x.y.z"
- Make a PR, merge when approved
git tag -a x.y.z -m "Version x.y.z"
git push origin bump/x.y.z && git push --tags
pod trunk push Purchases.podspec
carthage build --archive
- Create a new github release
- Upload to the new release
Purchases.framework.zip
- Create a branch bump/a.b.c, where a.b.c is the next version of the app after this release.
- Update the version number in
RCPurchases.m
,Purchases.podspec
and inPurchases/Info.plist
to the snapshot version for the next release, i.e.x.y.z-SNAPSHOT
git commit -am "Preparing for next version"
git push origin bump/a.b.c
- Make a PR for the snapshot bump, merge when approved