Combine the release_perform and release_publish Fastlane lanes
#119
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Currently, performing a release once the release PR has been merged involves invoking two commands:
bundle exec fastlane ios release_perform. This creates the tag and pushes it to the remote.bundle exec fastlane ios release_publish. This publishes the pod spec to the Cocoapods trunk.This is a leftover from the old release scripts, before the new release CLI, as the process had multiple steps. This PR simplifies the new process by merging the
release_performandrelease_publishsteps into a singlereleasestep (lane).Testing
Checklist