Move MIGRATION.md entry under the 7.0.0 section, as it was already released then

Author: iangmaia

MIGRATION.md

@@ -2,10 +2,6 @@
 
 ## From `8.0.0` to `9.0.0`
 
-- 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.swift` isn'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_release` for commiting the `.po/.pot` file
 - 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.
   - 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.
 - 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`.
@@ -20,3 +16,10 @@ In case of passing false as parameter or not providing a value (false being the
 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](https://github.com/wordpress-mobile/WordPress-Android/blob/0c64cb84c256e004473e97d72b4ac6682ebc140b/fastlane/lanes/release.rb#L86), 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`](https://docs.fastlane.tools/actions/push_to_git_remote/) command before this trigger to keep the existing behavior.
+
+## From `6.0.0` to `7.0.0`
+
+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.swift` isn'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_release` for commiting the `.po/.pot` file