Skip to content

Commit d561b93

Browse files
committed
Update MIGRATION.md with details on how to handle the latest breaking changes
1 parent 1f32098 commit d561b93

File tree

1 file changed

+16
-1
lines changed

1 file changed

+16
-1
lines changed

MIGRATION.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,21 @@
11
# Migration Instructions for Major Releases
22

3-
### From `7.0.0` to `8.0.0`
3+
## Migrating to Trunk
4+
5+
- Ensure that calls to `ios_bump_version_release` already passed `skip_glotpress: true`.
6+
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:
7+
- `download_metadata.swift` isn't being used; if it is, it's a good time to migrate to the new tooling
8+
- You're not relying on `ios_bump_version_release` for commiting the `.po/.pot` file
9+
- The deprecated actions `ios_localize_project` and `ios_update_metadata` were now completely removed. If your project is still using them, please use the new tooling instead.
10+
- See `ios_generate_strings_file_from_code`, `ios_extract_keys_from_strings_files`, `ios_download_strings_files_from_glotpress` and `ios_merge_strings_files` for typical replacements.
11+
- The action `ios_get_app_version` now requires a parameter `public_version_xcconfig_file` with the public `.xcconfig` file path instead of relying on the environment variable `PUBLIC_CONFIG_FILE`. While the complete removal of this environment variable is our goal, at this point it is still required by other actions such as `ios_bump_version_release` and `ios_codefreeze_prechecks`.
12+
- The usage of a `Deliverfile` (including its `app_version`) is discouraged -- please use `upload_to_app_store` directly from your `Fastfile` instead. Therefore, the parameter `skip_deliver` from the actions `ios_bump_version_hotfix` and `ios_bump_version_release` has been removed.
13+
14+
### Clean-ups
15+
16+
- You can now delete the `ENV['APP_STORE_STRINGS_FILE_NAME']` from your Fastfile, as it isn't being used anymore.
17+
18+
## From `7.0.0` to `8.0.0`
419

520
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.
621

0 commit comments

Comments
 (0)