Adds clarification to two steps of the Release Checklist:
Handling merge conflicts during a betafix:
Mark all 4 PRs ready for review and request review from your release wrangler buddy. In some release cases (like betafixes), it's likely that the PRs could have conflicts with trunk. In this case, do not resolve merge conflicts by merging with trunk as this will introduce new and unexpected changes into the release. Instead, leave the conflicts until the release is integrated into the main apps, and then resolve the conflicts when merging the PRs back to trunk. Optionally, a second clone of the release branch can be created to verify the CI checks.
Publishing a release.
Create a new gutenberg-mobile GitHub Release. Include a list of changes in the Release description. Ensure the checkmark next "Set as the latest release" is checked, and publish the release with the "Publish release" button.
Adds clarification to two steps of the Release Checklist:
Handling merge conflicts during a betafix:
Publishing a release.
Fixes: