-
Notifications
You must be signed in to change notification settings - Fork 219
Conversation
The release pull request has been created! This checklist is a guide to follow for the remainder of the release process. You can check off each item in this list once completed.
Initial Preparation
Write Testing NotesWhen creating testing notes, please write them from the perspective of a "user" (merchant) familiar with WooCommerce. So you don't have to spell out exact steps for common setup scenarios (eg. "Create a product"), but do be specific about the thing being tested. Include screenshots demonstrating expectations where that will be helpful. Additionally, make sure to differentiate between things in the testing notes that only apply to the feature plugin and things that apply when included in WooCommerce core as there may be variations there.
Update Pull Request description and get approvals
Ensure hub is set up and you're authenticated
Push the button - Deploy!
If this release is deployed to WordPress.org...
After Workflow completes
Publish posts
Pull request in WooCommerce Core for Package updateThis only needs to be done if this release is the last release of the feature plugin before code freeze in the WooCommerce core cycle. If this condition doesn't exist you can skip this section.
🚀 This comment was generated by the automations bot triggered by the creation of the branch:
|
Size Change: -853 B (0%) Total Size: 862 kB
ℹ️ View Unchanged
|
…6007 Add feature gate for the global styles for Product Sale Badge block
we want to always load lazy loaded components from their default paths to avoid having to handle importing components in different ways for regular and atomic component packages
The Site Editor is expecting the footer parts to be there or it will try to load them anyways and throw a 404. It's not breaking, but it's polluting the console.
Previously, we used a util called `trashAllPosts` which navigated to the post UI and deleted all the posts to tear down any side-effects of template editing tests. However, with a [recent change](WordPress/wordpress-develop@14e20f7), WP Core removed the UI for those and that made our tests meet a 500 error. Using the REST API should also make everything faster.
was still present in attribute-filter.test.js
Before it was responsible for enabling translations for all the atomic blocks
This reverts commit dbb0fab.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I didn't test (I trust that @tarhi-saad did), the code looks good even thou it's really big.
Core PR is up woocommerce/woocommerce#32075 I've picked changes from this into trunk. |
This is the release pull request for WooCommerce Blocks plugin
7.2.0
.Dev Notes
Changelog
Communication
Prepared Updates
Please leave a comment on this PR with links to the following:
Quality
🚀 This pull request was generated by the automations bot triggered by the creation of the branch:
release/7.2.0
. cc @mikejolley