The WordPress team has introduced new guidelines for syncing code from the Gutenberg repository into the wordpress-develop repository. This change, which affects developers, shifts the method from using npm packages to downloading zip files of built assets from GitHub.
Change in Synchronization Method
The method for importing code has changed significantly. Instead of relying on npm packages, developers will now download zip files containing built assets from the GitHub Container Registry. This aims to simplify the process and improve efficiency.
Synchronization Schedule
During the 7.1 release cycle, syncing will occur one week after each general release of Gutenberg. The goal is to move towards a more frequent syncing schedule, potentially weekly or even daily, to keep the trunk up to date with the latest changes.
Fixed Bugs
Two bugs that previously hindered updates to the wordpress-develop repository have been resolved. This allows for successful syncing with the latest Gutenberg release, currently at version 23.4.0, ensuring that developers can work with the most recent code.
Frequently Asked Questions
What is the new method for syncing code from Gutenberg?
The new method involves downloading zip files of built assets from the GitHub Container Registry instead of using npm packages.
When will syncing occur during the 7.1 release cycle?
Syncing will happen one week after each general release of Gutenberg.
What version of Gutenberg is currently synced with wordpress-develop?
The current version synced with wordpress-develop is 23.4.0.