A new 5-week release cycle to enhance the stability and reliability of WooCommerce.
Recent updates to error handling in 9.1 and optional remote error logging coming in 9.4 aim to simplify troubleshooting for developers and store owners.
๐ Coming in 9.4: โจ Improved Product Collection blocks ๐ Remote error logging improvements ๐ New express checkout customization options And more ๐
WooCommerce 9.3.2: Dot Release This release includes several fixes which affect CSV imports, stock notifications, and the checkout mini cart.
We’ve got a booth, a meetup, and more at WordCamp Europe this year! Take a read and find out what to expect.
WooCommerce 9.3.1 disables remote error logging, as this feature may obscure details about fatal errors. We plan to reintroduce the feature in WooCommerce 9.4.
WooCommerce 9.3 is here, featuring accessibility and user experience improvements, remote error logging, and more.
September Office Hours will be Wednesday, September 18 from 16:00 – 17:00 UTC in the #developers channel of the Woo Community Slack.
WooCommerce 9.3, introduces remote error logging, wp-admin stability improvements, a 27% file size reduction, and various accessibility enhancements.
We are releasing a PR (#50892), as part of 9.2.3 which fixes missing translations in the Cart and Checkout block
Two changes in WooCommerce 9.2 and 9.2.1 caused unexpected behavior with the WooCommerce iOS app and third-party plugins. This release reverts those changes.
What You Can Do with Woo WooCommerce is built for scaling; it can be run on everything from a small base server setup to a multi-million dollar cloud deployment processing millions of orders. It…
As part of the 9.2 release, we detected an increased number of errors when running final tests on the release on August 20th, 2024. This release reverts that specific commit.
Check out the latest releases, which includes more a11y updates in the block based checkout, more ways to customize stores, security improvements and more.
Hello developers! We will be back with office hours this month onย Wednesday, August 21 from 16:00 โ 17:00 UTC. This month, our very own Ellen Bauer will be joining the chat to talk about…
In February 2024 a number of new accessibility issue tickets popped up in the WooCommerce backlog, they mostly came from one person – Amber Hinds of Equalize Digital. You may have seen her name…
Join the GitHub Discussion and share your perspective on evolving product types to a more versatile trait system
WooCommerce 9.2 is coming soon… The post will track the work we do as we prepare to release 9.2 as well as provide a preview of what’s to come in this new version. Other…
WooCommerce 9.1.3 and 9.1.4 have been released Current Stable Tag ๐ WooCommerce 9.1.4 In this latest release, we’ve reverted a tracking feature due to unexpected spikes in usage and implementing a fix in order…
Welcome to a special edition post, brought to you by Beau Lebens, Head of Engineering for Woo. Today, I’d like to share some insight into our plans for WooCommerce, Wooโs core product, over the…
To ensure the continued security, performance, and scalability of the WooCommerce ecosystem, we are implementing stricter version requirements for certain extensions. This move is part of our ongoing efforts to modernize the WooCommerce codebase…
WooCommerce 9.1.2 has been released This release includes a fix for a separator issue in the flat rate shipping inputs. Current Stable Tag ๐ WooCommerce 9.1.2 ๐ Released July 12 2024 In 9.0.1 we detected…
The flat rate shipping bug from 9.0 has resurfaced due to a manual exclusion of the fix from 9.1. The details and the fix for the issue are exactly the same as in the…
WooCommerce 9.1.1 is has been released This release includes a revert of a commit that inadvertently interfered with the accessibility of the Checkout block. Current Stable Tag ๐ WooCommerce 9.1.1 ๐ Released July 11, 2024
We are issuing this advisory to alert the WooCommerce community about an accessibility issue found in the Checkout block of WooCommerce 9.1.0. The affected feature is being reverted today, however, see the workaround below…