The main motivation of this change is migrating to Ruby 3 which isn't compatible with older versions of release toolkit.
There aren't many android related breaking changes in the migration guide. The only one I can find is calling push_to_git_remote before triggering a new build. However, I didn't find any place that triggers new builds in the Fastfile. So, I did make any changes to it.
[ ] Call push_to_git_remote in order to trigger new builds with latest changes.
Update: ⚠️ I didn't make ⬆️ change because I don't see any action in Fastfile which triggers new CI builds.
[x] ios_get_app_version is updated in this PR to pass the new config file parameter.
[x] ios_localize_project is not used
[x] ios_update_metadata is not used
[x] This project does not use Deliverfile.
[x] This project does not call get_prs_list.
Test
I'm not familiar enough with the release-toolkit nor the app's release process to know which fastlane lanes are safe to run locally and repeatedly for debugging or testing purpose.
The main motivation of this change is migrating to Ruby 3 which isn't compatible with older versions of release toolkit.
There aren't many android related breaking changes in the migration guide. The only one I can find is calling
push_to_git_remote
before triggering a new build. However, I didn't find any place that triggers new builds in the Fastfile. So, I did make any changes to it.From the 7.0.0 to 8.0.0 migration guide
push_to_git_remote
in order to trigger new builds with latest changes. Update: ⚠️ I didn't make ⬆️ change because I don't see any action in Fastfile which triggers new CI builds.From the 8.0.0 to 9.0.0 migration guide
ios_get_app_version
is updated in this PR to pass the new config file parameter.ios_localize_project
is not usedios_update_metadata
is not usedDeliverfile
.get_prs_list
.Test
I'm not familiar enough with the release-toolkit nor the app's release process to know which fastlane lanes are safe to run locally and repeatedly for debugging or testing purpose.