We are pleased to announce the release of WooCommerce 6.0. This release should be backwards compatible with the previous version.
Due to internal process changes, the WooCommerce 6.0 release was delayed by one day. This allowed for us to complete some additional testing, and we don’t anticipate a delay for the WooCommerce 6.1 release.
As always, we recommend creating a backup of your site and making sure that your theme and any other plugins are compatible before updating. You can check out this update guide for more information.
What’s new in 6.0?
WooCommerce Blocks: We’ve updated to the 6.3.3 version of the feature plugin. See the release posts for 6.3.2 and 6.2.0 to find out what’s new.
WooCommerce Admin: We’ve updated to the 2.9.4 version of the feature plugin. See the changelog to find out what’s new.
Product Attribute Filtering: With this release, we are entering the final stages of delivering our revamp of product attribute filtering. We have removed the need for a code snippet to show the feature; both the feature flag and system tool is now available for all merchants.
Rate Limit Table: In order to address the performance issues caused by storing rate limits in the options table, we have created a new table to hold rate limit entries. See #30960 for more details.
These are just some of the changes that are included in WooCommerce 6.0. You can find the complete changelog for this release in the changelog.txt file.
Actions and Filters
This release adds two actions:
After the shipping options in the product data metabox. #30876
After the variations table on the add-to-cart form. #29642
This release adds two filters:
Allows filtering the ‘autocomplete’ attribute for quantity inputs. #31196
Filters the return value of the block template check. #30997
Thank you for pointing out this mistake! Sometimes when we receive community pull requests, they don’t bump the version, and if it gets missed during review, we won’t have it labeled appropriately for highlighting in the blog post. We’re currently looking at areas for automation in our pull request and release processes, so I’ve taken note of this.
I really wish this were written in a way that people who are primarily front-end developers could understand more readily. I get that a ton of work went into this release and appreciate the efforts of all the people noted above, but calling something “6.0” indicates a major release, and as someone who simply wants to be able to more or less “plug and play” WooCommerce into a client’s site, I have absolutely no idea from this article how this major release helps me in my work. This article seems written only for someone who deeply understands back-end stuff. Directing to the changelog for more details is great for a back-end developer, but it’s unintelligible to me.
Real-world usability: I would love to take advantage of the WC blocks, especially for the cart/checkout process, but previously the blocks weren’t compatible with Automattic’s own min-max quantities plugin. Has that changed? That’s the kind of high-level question I would like to see answered from a major release.
Thanks for the delayed email warning us about this version and the need to test on a staging site! Could you have sent this email out maybe a week ago??? I updated my sites that use Woocommerce without noticing it was version 6.0 and now today I get an email cautioning me against upgrading on a live site. Once I realized the update had already occurred (and then noticed it involved a database update too!) I had to revisit each account and make sure nothing broke. I and I’m sure others would appreciate these ‘warning’ emails well in advance of the update being pushed to the public!
Apologies for the trouble. I don’t think we send out any emails with releases (or after them), but generally, it’s a good idea to test any release on a staging site before updating live sites, especially when it comes to stores.