You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that WordPress 6.1 has been released, we should remove the back-compat code for WordPress 6.0 (in lib/compat/wordpress-6.0/) from Gutenberg. This is because Gutenberg supports the current and previous versions of WordPress (i.e 6.1 and 6.0); the code in lib/compat/wordpress-6.1/ is needed to allow it to work on a WP 6.0 installation (which lacks some code that is in 6.1). (OTOH, the lib/compat/wordpress-6.0/ dir is no longer needed, as it provides backwards compatibility for WP 5.9 and older; but those versions are no longer supported by Gutenberg.)
We should also look out for tests for that code in phpunit, make sure that those tests have been carried over to wordpress-develop (and add them there if they haven't), and remove them.
We might need to exercise a bit more care when removing code in lib/block-supports; I'm not entirely sure how that (unversioned) compat layer is applied to Gutenberg.
Now that WordPress 6.1 has been released, we should remove the back-compat code for WordPress 6.0 (in
lib/compat/wordpress-6.0/
) from Gutenberg. This is because Gutenberg supports the current and previous versions of WordPress (i.e 6.1 and 6.0); the code inlib/compat/wordpress-6.1/
is needed to allow it to work on a WP 6.0 installation (which lacks some code that is in 6.1). (OTOH, thelib/compat/wordpress-6.0/
dir is no longer needed, as it provides backwards compatibility for WP 5.9 and older; but those versions are no longer supported by Gutenberg.)We should also look out for tests for that code in
phpunit
, make sure that those tests have been carried over towordpress-develop
(and add them there if they haven't), and remove them.We might need to exercise a bit more care when removing code in
lib/block-supports
; I'm not entirely sure how that (unversioned) compat layer is applied to Gutenberg.cc/ @c4rl0sbr4v0 @ramonjd @oandregal @scruffian in case y'all wanna help with this 😊
The text was updated successfully, but these errors were encountered: