- The
prototype_build_details_commentaction have been updated to work with Firebase App Distribution instead of App Center [#630].- If you were using the
prototype_build_details_commentaction in concert with theappcenter_uploadaction, you'll need to migrate to usefirebase_app_distributionaction instead, then adjust the parameters forprototype_build_details_commentaccordingly (mostly removing theappcenter_upload-related ones likeapp_center_org_name). - If you were using the
prototype_build_details_commentaction out of the context of App Center but with adownload_urlinstead (e.g. Cloudfront URL), no update of the call site is needed.
- If you were using the
android_current_branch_is_hotfixno longer supports thebuild_gradle_pathparameter. Convert the project to defineversionNameandversionCodeinversion.propertiesand callandroid_current_branch_is_hotfixwithversion_properties_path.- Various helper methods and actions to calculate version bumps have been deleted (see
CHANGELOG.mdfor the full list). Use theVersioningmodule for any version computation or automation. Fastlane::Helper:Android::GitHelperandFastlane::Helper::Ios::GitHelperhave been removed. If you were using their respectivecommit_version_bumpmethods, you'll need to run the commit directly in yourFastfile, for example via Fastlane'sgit_commitaction.android_tag_buildandios_tag_buildhave been removed. Our recommended workflow for tagging releases relies on GitHub creating a tag when a GitHub release is published.create_releasehas been removed. Usecreate_github_releaseinstead.
- The
ios_check_beta_depsnow uses thePodfile.lockinstead ofPodfilefor its detection. If you called this action with an explicitpodfile: …argument, you'll have to update the call to uselockfile:instead—or remove that argument completely from your call and rely on its default value beingPodfile.lock.
- The new minimum required Ruby version is
3.2.2. Please make sure to upgrade your projects before upgrading to this version to avoid compatibility issues. - Action
setbranchprotectionhas been renamedset_branch_protection. Besides, you might want to use the newcopy_branch_protection(from_branch: to_branch:)instead (especially for protecting therelease/*branch with the same settings astrunkafter a code-freeze). - Action
removebranchprotectionhas been renamedremove_branch_protection. - Action
setfrozentaghas been renamedset_milestone_frozen_marker. - Actions
ios_clear_intermediate_tagsandios_final_taghave been removed, as they have been deprecated for a while. - Option
has_alpha_versionhas been removed after being deprecated for a while. - Options
project_nameandproject_root_folderhave been removed from several actions. Explicit paths should be passed instead. - Action
update_pull_requests_milestonehas been renamedupdate_assigned_milestoneand itspr_numbersandpr_commentparameters renamed to justnumbersandcomment; the action now acts on Issues and not just PRs anymore.
- The deprecated actions
ios_localize_projectandios_update_metadatawere now completely removed. If your project is still using them, please use the new tooling instead.- See
ios_generate_strings_file_from_code,ios_extract_keys_from_strings_files,ios_download_strings_files_from_glotpressandios_merge_strings_filesfor typical replacements.
- See
- The action
ios_get_app_versionnow requires a parameterpublic_version_xcconfig_filewith the public.xcconfigfile path instead of relying on the environment variablePUBLIC_CONFIG_FILE. While the complete removal of this environment variable is our goal, at this point it is still required by other actions such asios_bump_version_releaseandios_codefreeze_prechecks. - The usage of a
Deliverfile(including itsapp_version) is discouraged -- please useupload_to_app_storedirectly from yourFastfileinstead. Therefore, the parameterskip_deliverfrom the actionsios_bump_version_hotfixandios_bump_version_releasehas been removed. - The
get_prs_listaction has been removed, as it was not used by client apps anymore. If you were still calling it, check if it was still necessary (were you still doing anything with the file it generated?). If you need to generate a list of PRs for other needs—especially generating GitHub Pre-Release or App Center notes for beta builds—you might consider checkingget_prs_between_tagsinstead, which behaves slightly differently (listing PRs that landed between two builds/tags, rather than PRs associated with a milestone) but should be more flexible and more appropriate for those kind of use cases.
- You can now delete the
ENV['APP_STORE_STRINGS_FILE_NAME']from your Fastfile, as it isn't being used anymore. - When using the
upload_to_s3action, replace any use of itsskip_if_exists: trueparameter (resp.false) withif_exists: :skip(resp.:fail).
We are no longer pushing to remote after creating a new commit or a branch. That means, developers need to manually push the changes or add push commands in the project's Fastfile. Most importantly, we can no longer immediately trigger beta/final builds after creating a new commit because the changes will not be in remote yet. If you want to keep the existing behavior, you'll need to add a push command before these triggers.
For example, in WordPress-Android's new_beta_release lane, we download translations, bump the beta version and then trigger a new build in CI. After migrating to 8.0.0 of release-toolkit, we'll need to add push_to_git_remote command before this trigger to keep the existing behavior.
Ensure that calls to ios_bump_version_release already passed skip_glotpress: true.
In case of passing false as parameter or not providing a value (false being the default for this ConfigItem), you'll have to ensure that:
download_metadata.swiftisn't being used; if it is, it's a good time to migrate to the new tooling- You're not relying on
ios_bump_version_releasefor commiting the.po/.potfile