Conversation
🟢 Test new changes (Android)Build: pr16764-0dfb596 |
🟢 Writing Flow checklist (Android)Build: pr16764-0dfb596 General
Rich Text Format
Splitting and merging
Undo / Redo - Test Cases |
🟢 Test new changes (iOS)Build: pr18895-74c5bdb
1 Skipped as it is for Android only. |
🟢 Writing Flow checklist (iOS)Build: pr18895-74c5bdb General
Rich Text Format
Splitting and merging
Undo / Redo - Test Cases |
dcalhoun
left a comment
There was a problem hiding this comment.
LGTM! 🚀
My understanding is that we need to create a new GitHub Release based upon this branch prior to resolving conflicts and merging. Is that correct?
After that, we'll need to resolve conflicts and generate a bundle before merging.
# Conflicts: # bundle/ios/App.js # bundle/ios/App.js.map # gutenberg
@dcalhoun That's correct, the tag created via the GitHub release should point to the latest commit of the release branch before the Gutenberg reference points to the merge commit from Gutenberg's
I've done this in the following commits: |
Release for Gutenberg Mobile 1.78.1
Related PRs
Extra PRs that Landed After the Release Was Cut
No extra PRs yet. 🎉
Changes
Change 1
v1WordPress/gutenberg#41533v1WordPress/gutenberg#41465Change 2
Test plan
Once the installable builds of the main apps are ready, perform a quick smoke test of the editor on both iOS and Android to verify it launches without crashing. We will perform additional testing after the main apps cut their releases.
Release Submission Checklist
RELEASE-NOTES.txtis updated with all the changes that made it to the release. ReplaceUnreleasedsection with the release version and create a newUnreleasedsection.gutenberg/packages/react-native-editor/CHANGELOG.mdis updated with all the changes that made it to the release. Replace## Unreleasedwith the release version and create a new## Unreleased.