Closed jyu115 closed 6 months ago
So from Step 1 to Step 3 will be on a separate branch -> which will be reviewed by the team.
Once the branch is merged into master, thats when we run fastlane ios release_sdk
right?
Does it also take care of uploading the zip files? Or will that need to be uploaded from build folder to tags?
So from Step 1 to Step 3 will be on a separate branch -> which will be reviewed by the team. Once the branch is merged into master, thats when we run
fastlane ios release_sdk
right? Does it also take care of uploading the zip files? Or will that need to be uploaded from build folder to tags?
Yes I think the best process would be: 1) Step 1 to Step 3 on a separate branch and merge to master. 2) Run a github actions workflow -- this takes care of uploading zip files and creating a release
🔹 Jira Ticket(s)
Description
Implemented https://fastlane.tools/ to automate iOS SDK release. Also uses a fastlane plugin create_xcframework.
Steps to release in the new process:
CHANGELOG.md
sdkVersion
variable inIterableAPI.swift
CHANGELOG.md
andIterableAPI.swift
changes to the branchfastlane ios release_sdk
It will prompt you to enterrelease version number
(e.g. 6.5.0-beta) andoutput directory
(e.g. build2)That's it! When
release_sdk
lane is run, it will run these lanes in subsequent order:bump_release_version
clean_and_lint
build_xcframework
tag_version
pod_trunk_push
Github release created with assets uploaded:
Finished success status:
See available lanes: