WordPress 6.3 compatibility

[jeherve]

WordPress 6.3 is set to release on August 8, 2023.

• Planning: make.wordpress.org/core/6-3

Let's use this issue to keep track of anything that may come up until then.

• Update our "tested up to" version to 6.3 General: indicate compatibility with upcoming WP 6.3 #31910
• Update the version of WordPress required for Jetpack from WP 6.1 to WP 6.2: On hold for now, waiting for 12.6 General: update WordPress requirements to WP 6.2 #32762
• Remove 6.1 backward-compatible checks On hold for now, waiting for 12.6 General: remove WP 6.1 backwards compatibility checks #32772

In addition to the above, we can follow the dev-notes that will drop here about the release:
make.wordpress.org/core/tag/dev-notes+6-3

• Layout updates: changes in CSS specificity
• WP_Query used internally in get_pages()
• Improved Caching for Database Queries in WP_User_Query
• Image performance enhancements in WordPress 6.3: ensure that those enhancements do not conflict with our Lazy Images implementation.

Below, let's keep track of things we can start implementing once WordPress 6.3 is the minimum required version, in #32865.

• Assets: switch to registering scripts with async and defer attributes introduced in WordPress 6.3 #32852
• Layout updates: __experimentalLayout is now layout #32853
• Code modernization: Replace usage of strpos with str_starts_with #32854
• Code modernization: Replace usage of strpos with str_contains #32863
• Code modernization: Replace usage of substr with str_starts_with and str_ends_with #32864

---

For reference: prior art for WordPress 6.2 compat: #27795

[jeherve]

Improved Caching for Database Queries in WP_User_Query

@Automattic/jetpack-kernel Do you think this is something that may impact us in sync?

[sergeymitr]

Thanks for the ping @jeherve, there might be an issue here.

@bisko, it looks like we're querying user ID's directly from the database, and then use WP_User_Query to fetch users by those ID's here.
Do you think there might be a problem with users being in the database, but WP_User_Query operating with an older cache and not finding those users?
Technically it shouldn't happen as the cache gets invalidated every time there's a change to the database, but it will occasionally happen, so may be we only should make sure it fails gracefully if that happens.