This repository has been archived by the owner on Feb 23, 2024. It is now read-only.
Release: 11.5.3 #11706
Merged
Release: 11.5.3 #11706
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
#11455) In WordPress 6.4, it appears that the global `have_posts` is `false` in the context of the full site editing single product template. This breaks the Classic Template block. In this commit, we are creating a custom query using the available id instead of relying on the global query. This might be a temporary workaround as we are waiting to see if that's an issue that core is willing to fix, as it might affect backwards-compatibility for other vendors. (cherry picked from commit d9e8809)
…11690) * Add protection towards wrong params in get_block_template_fallback() * Improve protection
* Fix pattern description * Decode the actual file content, not the filepath
…by AI (#11659) * Use wp_post table instead wp_option to store patterns data generated by AI * avoid crash when there isn't any patterns_ai_data post type * restore check * remove unnecessary constant * catch error * pass boolean to return WP_Error
* Rename Centered Header Menu with Search pattern Since the search bar has been removed from this pattern, this PR renames the pattern title and slug to reflect that change. * Rename file to reflect search removal. Remove `search` from the filename, as this no longer reflects the pattern.
* fix pattern route performance * update namespace * improve middleware * improve ProductSchema * improve error handling * update identifier * fix middleware * update description * use schema to return the response * Break down the generate_content method and create the new fetch_dummy_products_to_update method for handling the fetch of dummy products to be updated. * Ensure the Product endpoint relies on the fetch_dummy_products_to_update method for fetching dummy products to avoid code repetition and add safety checks and handle errors in case certain properties are not available. * Add error handling for the Products endpoint. * Remove memory limit increase and update docblocks. * re-add set_time_limit --------- Co-authored-by: Patricia Hillebrandt <[email protected]>
…locks into release/11.5.2
…locks into release/11.5.2
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.
Push the button - Deploy
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. Reviewing and merging the PR is your team's responsibility, except in the case of
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:
|
* Fix pattern description * Decode the actual file content, not the filepath
gigitux
force-pushed
the
release/11.5.3
branch
from
0d3666e
to
bc6d510
Compare
…locks into release/11.5.3
|
The release ZIP for this PR is accessible via: Script Dependencies ReportThe
This comment was automatically generated by the TypeScript Errors Report
assets/js/blocks/collection-filters/inner-blocks/price-filter/price-slider/inspector.tsx
assets/js/blocks/collection-filters/utils.ts assets/js/blocks/product-gallery/inner-blocks/product-gallery-large-image/frontend.tsx |
|
Size Change: 0 B Total Size: 1.54 MB ℹ️ View Unchanged
|
lsinger
approved these changes
Nov 8, 2023
There was a problem hiding this comment.
Changes look good to me and the unit tests in Core pass with this change applied to woocommerce/woocommerce#41269 as well. 🚢
|
Heads-up that the failing tests in the Playwright Tests / Playwright E2E tests - SideEffects job are the ones skipped in this PR: #11700. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Patch release
This is the patch release pull request for WooCommerce Blocks plugin
11.5.3.Changelog
Communication
Prepared Updates
Please leave a comment on this PR with links to the following:
Developer Notes - The following issues require developer notes in the release post:
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/11.5.3. cc @gigitux