Steve-Dee-Designs
/
woocommerce
mirror of https://github.com/woocommerce/woocommerce.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'release/10.8.0' of https://github.com/woocommerce/woocommerce-blocks into trunk

This commit is contained in:
Luigi 2023-08-11 17:09:13 +02:00
parent f9ee3cfd70 fa8ef7098e
commit 11e335d750
3 changed files with 33 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
plugins/woocommerce-blocks/docs/internal-developers/testing/releases/1083.md Normal file
View File

@ -0,0 +1,24 @@
# Testing notes and ZIP for release 10.8.3
Zip file for testing: [woocommerce-gutenberg-products-block.zip](https://github.com/woocommerce/woocommerce-blocks/files/12322309/woocommerce-gutenberg-products-block.zip)
## WooCommerce Core
### Create wc-all-block-styles chunk with all blocks stylesheet for classic themes. [#10543](https://github.com/woocommerce/woocommerce-blocks/pull/10543)
⚠️: Following these testing instruction for a classic theme (Storefront) and a block theme (TT3)
#### For classic theme ensure that is loaded only `wc-all-blocks-style.css` and `wc-blocks-vendors-style.css` stylesheets
#### For block theme sure that is loaded only the stylesheets of blocks visible in the page
1. Create a post or page and add the All Products block. Verify styles are loaded correctly.
2. Visit the page in the frontend and verify styles are loaded correctly in the frontend as well.
3. Repeat steps 1 and 2 with all blocks listed on [this page](https://wordpress.org/plugins/woo-gutenberg-products-block/). Make sure to test each block individually. So, when possible, try with only one block on the page (in some cases, that's not possible, ie: filter blocks, in that case, try with as few blocks as possible on the page). The reason is that we want to make sure each block includes the style dependencies that it needs, so they need to be tested in isolation, otherwise styles from other blocks might leak into other blocks and "help fix issues".
### Fix the "On Sale" badge position. [#10550](https://github.com/woocommerce/woocommerce-blocks/pull/10550)
1. Enable the `Storefront` theme.
2. Create a new page or post.
3. Add the `Products by Attribute`, `Products by Tag`, `Products by Category`, `Handpicked products` and `All products` blocks.
4. Check the `Sale` back shows on the top-right corner of the image on all of them, in the editor and in the frontend.

1
plugins/woocommerce-blocks/docs/internal-developers/testing/releases/README.md
View File

@ -168,6 +168,7 @@ Every release includes specific testing instructions for new features and bug fi
- [10.8.0](./1080.md)
- [10.8.1](./1081.md)
- [10.8.2](./1082.md)
- [10.8.3](./1083.md)
<!-- FEEDBACK -->

9
plugins/woocommerce-blocks/readme.txt
View File

@ -4,7 +4,7 @@ Tags: gutenberg, woocommerce, woo commerce, products, blocks, woocommerce blocks
Requires at least: 6.2
Tested up to: 6.2
Requires PHP: 7.3
Stable tag: 10.8.2
Stable tag: 10.8.3
License: GPLv3
License URI: https://www.gnu.org/licenses/gpl-3.0.html
@ -81,6 +81,13 @@ Release and roadmap notes available on the [WooCommerce Developers Blog](https:/
== Changelog ==
= 10.8.3 - 2023-08-11 =
#### Bug Fixes
- Create wc-all-block-styles chunk with all blocks stylesheet for classic themes. ([10543](https://github.com/woocommerce/woocommerce-blocks/pull/10543))
- Fix the "On Sale" badge position. ([10550](https://github.com/woocommerce/woocommerce-blocks/pull/10550))
= 10.8.2 - 2023-08-09 =
#### Bug Fixes