-
Notifications
You must be signed in to change notification settings - Fork 219
Conversation
…or showBillingFields (#7393) Co-authored-by: Niels Lange <[email protected]>
…ng in the Checkout block in the editor (#7434) * Construct args for canMakePayment with correct keys * When the CheckoutEventsContext mounts, initialize payment store * Destructure useSelect correctly * Dispatch __internalInitializePaymentStore in selector tests * Update selector name to __internalUpdateAvailablePaymentMethods * Remove check for editor when registering checkout store * Add check for when express payment methods have updated too * Ensure billingAddress key exists in canMakePayment arg * Use editor context to know if we're in editor
…ackground color (#7510) Co-authored-by: Albert Juhé Lluveras <[email protected]>
* Fixed Price Slider Issue Located where the price slider was hard coded and replaced it. * fix CSS lint * use currentColor instead of hard-coded color for the slider of the Filter By Price block #7130 use currentColor instead of hard-coded color for the slider of the Filte By Price block * use currentColor instead of hard-coded color for the slider of the Filter By Price block #7130 use currentColor instead of hard-coded color for the slider of the Filte By Price block * remove background-color Co-authored-by: EmptySet-Exe <[email protected]> Co-authored-by: Niels Lange <[email protected]>
…r in dark themes (#7525)
* fix inconsistent button styling with TT3 * use wc_wp_theme_get_element_class_name * add check to be sure that wc_wp_theme_get_element_class_name function exists
Patch release stepsThe release pull request has been created! This checklist is a guide to follow for the remainder of the patch release process. You can check off each item in this list once completed.
Initial Preparation
Create the Testing Notes
Each porter is responsible for testing the PRs that fall under the focus of their own team. Shared functionality should be tested by both porters. This means that the Rubik porter will mostly test checkout blocks and Store API endpoints, while the Kirigami porter will test the product related blocks and Store API endpoints.
Update Pull Request description and get approvals
If this release is deployed to WordPress.org
After Deploy
Pull request in WooCommerce Core for Package updateThis only needs done if the patch release needs to be included in WooCommerce Core.
Publish PostsYou only need to post public release announcements and update relevant public facing docs if this patch release is deployed to WP.org. Otherwise, you can skip this section.
🚀 This comment was generated by the automations bot triggered by the creation of the branch:
|
8427aec
to
667a7b5
Compare
968cc2e
to
c5c0a41
Compare
c5c0a41
to
69b5cc5
Compare
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.
Works as expected as well. Thanks @gigitux!
The release ZIP for this PR is accessible via:
|
Size Change: +116 B (0%) Total Size: 967 kB
ℹ️ View Unchanged
|
Patch release
This is the patch release pull request for WooCommerce Blocks plugin
8.7.6
.Changelog
Communication
Prepared Updates
Please leave a comment on this PR with links to the following:
Quality
Testing Instructions are included in this PR
Any performance impacts are documented.
🚀 This pull request was generated by the automations bot triggered by the creation of the branch:
release/8.7.6
. cc @gigitux