Merged
Conversation
GOOWOO-372-populate-gladata-with-the-serviceBasedMerchant-property
…rchant setup complete
…g-flow-update Update flow
…ponents Add ConnectedGoogleAdsOnlyAccountCard component
…OOWOO-364-onboarding-flow-update
…low-update Implement new setup flow for service-based merchants
GOOWOO-380-rest-endpoint-to-mark-service-based-merchant-setup-complete
…for-sbm Tailor content for service-based merchants
…api-pull-mode-for-all-users [GOOWOO-483] Disable API Pull mode for all users
…-based-merchants Feature: Service Based Merchants
…lures Update notification-schedule e2e tests after API pull sync mode updates
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## trunk #3279 +/- ##
=========================================
+ Coverage 66.8% 66.8% +0.1%
- Complexity 5095 5152 +57
=========================================
Files 867 886 +19
Lines 26180 26682 +502
Branches 1466 1551 +85
=========================================
+ Hits 17479 17836 +357
- Misses 8528 8646 +118
- Partials 173 200 +27
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
Collaborator
What's Changed[Add] New Features 🎉
[Update] Updated ✨
[Fix] Fixes 🛠
[Dev] Developer-facing changes 🧑💻
New Contributors
Full Changelog: 3.5.2...3.5.3 |
This file contains hidden or 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
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
wooreleaseinstalled 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_versionclass of each migration class to be the same value as the version that is to be released.x.x.xis 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.phpinsidesrc/DB/Migration/, you should open that file and in the methodget_applicable_versionreturn1.12.0.ywhen 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 entrysection, or assigning thechangelog: nonelabel.You can also edit the changelog manually in the
woorelease releasestep later./tmp/google-listings-and-ads.zipfile on a test siteNext steps
When releasing to WordPress.org, “release notifications” have been enabled, so each committer will be sent an email with an action link to confirm the release. This must be done after committing in SVN before the release becomes available. See the following page for releases pending notifications: https://wordpress.org/plugins/developers/releases/
trunktodevelop(PR), if applicable for this repo.