WordPress 6.2 compatibility

[jeherve]

WordPress 6.2 is set to release on March 28, 2023.

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

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

• Update our "tested up to" version to 6.2 -> General: indicate compatibility with upcoming WP 6.2 #29341
• Update the version of WordPress required for Jetpack from WP 6.0 to WP 6.1: On hold for now, see p9dueE-6vE-p2#comment-9128
• Remove 6.0 backward-compatible checks On hold for now, see p9dueE-6vE-p2#comment-9128
• Non-plain-text block description is being deprecated in WordPress 6.2 Non-plain-text block description is being deprecated in WordPress 6.2 #26792
  • Discussion is still ongoing on the better solution for this (see Non-plain-text block description is being deprecated in WordPress 6.2 #26792). Blocks: only use strings in block descriptions #29757 is the PR that would just remove the deprecation notices, if we decide to go with that.
• Blocks: remove deprecated selector Blocks: remove deprecated selector #28719
• get_page_by_title is now deprecated (source)
• Deprecating bottom margin on control components (source)
• Changes to inline styles for InputControl and UnitControl (source) (in VideoPress)
• position prop is now deprecated for Dropdown and URLPopover (source)
• Switch to switch_to_user_locale instead of switch_to_locale( get_user_locale() ) (source) -- Not useful for us, we only do switch_to_locale( get_user_locale() ) in one place, where we rely on get_user_locale() to get the current user by default. Switching to switch_to_user_locale would mean that we would have to fetch the user, which wouldn't be simpler.
• Update InspectorControls now that __experimentalGroup is stabilized (source) (in VideoPress) VideoPress: Update comment on deprecated prop to mark it for later change #29541
• Remove usage of Requests. (source)
  • Pinterest: remove type hinting in function parameter #29505
  • API endpoints: handle updated Requests library #29542
  • It's still used in some of our tests (see Jetpack: Fix tests for core's new Requests library #27981). In this case, let's remove all those conditionals once we make WordPress 6.2 the minimum required version.

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-2

As a bonus, there are new features we may be able to start using in some parts of the codebase, either now with a safeguard or once WordPress 6.2 is the minimum required version in Jetpack:

• WP_HTML_Tag_Processor (source) Refactor ImageCDN parsing to rely on HTML API instead of RegExps #32700

---

For reference: prior art for WordPress 6.1 compat: #25417
Internal: p9dueE-6vE-p2

[coder-karen]

Linking to this internal post as well with more info about dates and planning: p9dueE-6vE-p2

[jeherve]

Changes to inline styles for InputControl and UnitControl (source)

any class names applied to the UnitControl component through its className prop will be applied to its outer wrapper element, instead of an inner input wrapper element.

@Automattic/jetpack-agora I see that VideoPress is using custom className on NumberControl and RangeControl. It may be worth taking a look and making sure nothing breaks layout with WordPress 6.2.

[dhasilva]

I see that VideoPress is using custom className on NumberControl and RangeControl. It may be worth taking a look and making sure nothing breaks layout with WordPress 6.2.

I updated my local version to 6.2-RC2 and there seems to be no regressions with the components that use the custom className on NumberControl or RangeControl 👍