-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release 2.4.11 #2010
Merged
Merged
release 2.4.11 #2010
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
to serve a consistent, easy to follow release checklist, and reduce redundancy in wiki pages. Requires woocommerce/grow#58
Release/2.4.10
…l-tags Fix the parent options being rendered as the selected tags in the TreeSelectControl
…hp8-1 Enable unit testing for PHP 8.1
…-attribute-table Add Empty Data placeholder in Attribute Mapping Table
This reverts commit 2f3d6e8.
…ing development builds" This reverts commit 52abc57.
Add a step to publish the latest extension build for the `develop` branch
…ippingTimes` actions
…they may throw an error
Remove an unused hook `useCallbackOnceEffect`
…emove most "Please try again later." from messages in the actions.js
…esult-notification Avoid continuing to sync settings with GMC after shipping time API failed
…cationCode action. Address: #1999 (comment)
…ExceptionWithResponseData when failed
…s called by `CountryCodeTrait`'s callbacks to avoid multiple namespaces. Address: #2004 (comment)
Add PHP tests for `CountryCodeTrait` and two related API controllers
Add client name and version as request headers
…_google_service_exception_errors`.
Update Asset Groups Texts
…service_exception_errors`. Address: #2007 (comment)
…rror-messages Adjust the infrastructure to uniform the error messages returned from Google Shopping Content service
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## trunk #2010 +/- ##
=========================================
+ Coverage 57.5% 58.1% +0.5%
- Complexity 4111 4119 +8
=========================================
Files 456 455 -1
Lines 17655 17688 +33
=========================================
+ Hits 10158 10271 +113
+ Misses 7497 7417 -80
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Checklist
woorelease
installed and set up.readme.txt
(keep the last two versions, since we will be adding a third during the release), commit changes.src/DB/Migration/
), modify their applicable version set in theget_applicable_version
class of each migration class to be the same value as the version that is to be released.x.x.x
is not a valid version and should be set manually with the new version. So, for example, if we are releasing version 1.12.0 and there is a fileMigration20211228T1640692399.php
insidesrc/DB/Migration/
, you should open that file and in the methodget_applicable_version
return1.12.0
.y
when prompted: "Would you like to add/delete them in the svn working copy?"Check if some entries are missing, need rewording, or need to be deleted. You can edit respective PRs by changing their title,
### Changelog entry
section, or assigning thechangelog: none
label.You can also edit the changelog manually in the
woorelease release
step later./tmp/google-listings-and-ads.zip
file on a test siteNext steps
trunk
todevelop
(if applicable for this repo).