Starting with version 5.6, WooCommerce Stripe will transition to a new version support policy that aligns with WooCommerce’s overarching L-2 version support policy.
WooCommerce Stripe currently supports versions of WordPress back to 4.6 and versions of WooCommerce back to 3.3.
Starting with the upcoming 5.5.0 release, WooCommerce Stripe will begin shifting to a version support policy that matches WooCommerce’s overarching L-2 support policy. This means we will support the latest minor release of WooCommerce and WordPress core, along with the previous two before that.
“Why?” or “Why now?” you may ask. We plan to improve the visual appeal of the setting’s UI in version 5.6.0 of WooCommerce Stripe by using WordPress and WooCommerce components and introducing some new features to help with the Stripe checkout process.
With these changes, we will need to rely more heavily on the installed WordPress and WooCommerce versions. We don’t want to increase the codebase’s complexity or decrease the plugin’s performance (both in terms of execution speed and plugin size).
How can I tell if this affects me?
This transition affects both merchants who use WooCommerce Stripe and developers who build solutions with it.
This change will affect you if you’re using either:
- WordPress 5.5.x or lower
- WooCommerce 5.4.x or lower
In the release of WooCommerce Stripe 5.5.0, we will include a notice in
wp-admin. This notice informs you if the version of WordPress and WooCommerce you’re using will not be supported.
What action should I take?
As always, we recommend stores run the latest release of WooCommerce. If you are running a version of WordPress or WooCommerce that is affected, we recommend that you update to the latest release.
There are instructions for updating WooCommerce and updating WordPress in the WooCommerce Docs.
Merchants using WooCommerce Stripe will only receive support if they are running versions of WooCommerce and WordPress that fall within the L-2 range for that release.
Thank you, as we continue to bring improvements to our plugin and our platform!
Note: An earlier version of this post incorrectly listed version numbers and corresponding release dates on which changes would occur. This has been corrected above.