Conversation
Was commented with "Remove when Jetpack requires WordPress 6.7".
…ld be `*Test.php` now.
… June 30th, 2025"
…d the workaround for brokenness in WP 6.7
|
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
|
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 Follow this PR Review Process:
If you have questions about anything, reach out in #jetpack-developers for guidance! Jetpack plugin: The Jetpack plugin has different release cadences depending on the platform:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Boost plugin: No scheduled milestone found for this plugin. If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Wpcomsh plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. |
Code Coverage SummaryCoverage changed in 7 files. Only the first 5 are listed here.
|
…ld be fixed by now." Not fixed after all.
| // Old Gutenberg packages' ESM builds don't fully specify their imports. Sigh. | ||
| // @todo Remove this when we upgrade @wordpress/dataviews to 11.2.0+. | ||
| // https://github.com/WordPress/gutenberg/issues/73362 | ||
| { | ||
| test: /\/node_modules\/@wordpress\/.*\/build-module\/.*\.js$/, | ||
| resolve: { fullySpecified: false }, | ||
| }, | ||
|
|
There was a problem hiding this comment.
Glad that we got rid of this.
manzoorwanijk
left a comment
There was a problem hiding this comment.
Looks fine to me. The test for 8.5 is stuck though.
|
That's because it's changed from "PHP tests: PHP 8.5 WP trunk" to "PHP tests: PHP 8.5 WP latest"; we'll need to unrequire the former and then require the latter instead. |
Closes MONOREP-332
Proposed changes:
@errorrather than@warntest-*.phptype filenames, all should be*Test.phpnow.wp_register_block_metadata_collectionand the workaround for brokenness in WP 6.7Other information:
Jetpack product discussion
#45518
p1769543281415539-slack-CDLH4C1UZ
Does this pull request change what data or activity we track or use?
No
Testing instructions: