Integrate gutenberg-mobile release 1.42.1 (fix) #13550
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up to #13540, using the right gutenberg-mobile tag for release 1.42.1.
As far as I can tell, #13540 was tested with the right branch, but this final commit updating to the release tag hash accidentally used the tag for
1.42.0
instead of1.42.1
.Comparing the previous tag in that PR (that it was tested with) to the one I'm using in this PR, you can see the change is only the tag update:
wordpress-mobile/gutenberg-mobile@3000ec...5d7a4d2
And that
release/16.3
without this PR is actually incorrectly pointing to gutenberg-mobile1.42.0
:https://github.com/wordpress-mobile/gutenberg-mobile/releases/tag/v1.42.0 (see that the hash is
6fed9e
)To test:
Should have already been tested in #13540, just check that this builds.
PR submission checklist:
RELEASE-NOTES.txt
if necessary.