Update from master to bring release v1.0 to develop #660
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Make sure the locale data is setup before importing anything, since block names get translated on import
The change there was for the unsupported blocks PR
…zation-priority Fix i18n initialization priority
* Update gutenberg ref * Add title vertical padding variables * Update gutenberg ref to point to release branch
…_image_color Revert wrong format-image color
Updated bundles
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR just brings the latest of master back to develop.
All work has been reviewed and tested during the release process so, will self-merge this.
On the Gutenberg side, it will also hold the ref to the merged release branch. TBDHad to revert the pointing to the merged release branch because the GB changes that brings in from GB master are breaking mobile.
We will temporarily point to a
rnmobile/developbranch on GB while we'll be working on porting the breaking changes. This way at least, ourdevelopwill be working fine so we can add work on top of it.