-
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.5.1 #2034
Merged
Merged
release 2.5.1 #2034
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
Provides the ability to control the product selection of synced products.
Add apply_filters hook to prepare_query_args
…n from `CampaignAssetsForm` to `AdaptiveForm`
…or `SetupFreeListings` and the relevant components
…nd `formProps` for `StoreRequirements` and the relevant components
…ding state of submit button in `SetupFreeListings` and `StoreRequirements`
…tupFreeListings` and the relevant components
Release 2.5.0 - Merge trunk into develop
…tion-request Move the verification request from `CampaignAssetsForm` to `AdaptiveForm`
Apply `AdaptiveForm` and its abilities to steps 2 and 3 of the onboarding flow for higher code consistent
Bumps [word-wrap](https://github.com/jonschlinkert/word-wrap) from 1.2.3 to 1.2.4. - [Release notes](https://github.com/jonschlinkert/word-wrap/releases) - [Commits](jonschlinkert/word-wrap@1.2.3...1.2.4) --- updated-dependencies: - dependency-name: word-wrap dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
Ability to control the product selection of synced products
…o rephrase a few messages
…tup` and remove unneeded codes
… listings form if any data is invalid
…lue equivalent to 0.
…d-wrap-1.2.4 Bump word-wrap from 1.2.3 to 1.2.4
…dress is having validation errors.
…e-validation-errors-step-2 Show validation errors on step 2 of the onboarding flow when unable to continue
…e-validation-errors-step-3 Show validation errors on step 3 of the onboarding flow when unable to continue
…oneNumberCard` tests. Address: #2027 (comment)
…er-card Add JavaScript tests for the `PhoneNumberCard` component
…er-contents Add JavaScript tests for the `EditPhoneNumberContent` and `VerifyPhoneNumberContent` components
Setup wp-env for E2E tests
Add To Cart Tracking support for Products (Beta) Block
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## trunk #2034 +/- ##
=========================================
+ Coverage 57.9% 58.1% +0.2%
- Complexity 4111 4119 +8
=========================================
Files 456 455 -1
Lines 17658 17695 +37
=========================================
+ Hits 10224 10278 +54
+ Misses 7434 7417 -17
Flags with carried forward coverage won't be shown. Click here to find out more.
|
[Add] New Features 🎉
[Update] Updated ✨
[Fix] Fixes 🛠
[Dev] Developer-facing changes 🧑💻
|
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).