Hello everyone,
Starting with the release of WooCommerce 4.2, we will be switching to a monthly release cadence! We’ve worked hard over the last year to increase both the frequency and stability of our releases, and we feel confident in taking this next step.
As of today, WooCommerce 4.2 is available for beta testing. You can either download it directly from WordPress.org or install our WooCommerce Beta Tester Plugin.
What’s new in 4.2?
As with our previous release, we have been continuing to focus on stability and performance in this cycle. You can review our changelog for the granular details, but here is a broad overview of what’s new:
WordPress Support Policy
Starting with the 4.2 release, we will adapt an L-2 sliding window support policy. What this means is that we are committed to ensuring that WooCommerce Core will work with the current WordPress version, as well as the two previous release branches.
You can read more about this new policy on our developer blog post.
New Hooks and Functions
We’ve added one new hook in this release:
| Filter | Description |
|---|---|
| woocommerce_menu_order_count | Enables filtering for the count of processing orders shown in the menu. |
We’ve also made some changes to a few hooks:
| Filter | Description |
|---|---|
| woocommerce_matched_rates | Added the customer as a third argument. |
| woocommerce_attribute_label | Fixed a bug that caused the prefix of global attributes to be removed from the second argument. |
Release Schedule
Here are our targets for the 4.2 release cycle:
| Version | Release |
|---|---|
| Beta | May 12th |
| Release Candidate | May 19th |
| 4.2 Release | June 2nd |
Testing
If you’d like to dive in and help test this new release, our handy WooCommerce Beta Tester plugin allows you to switch between beta versions and release candidates.
A set of testing instructions has been published on our Wiki page in GitHub. We’ve also posted a helpful writeup on beta testing to help get you started.
If you discover any bugs during the testing process, please let us know by logging a report in GitHub.
Thanks to all of our testers and contributors!
Leave a Reply