-
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.8.0 #2483
Merged
Merged
Release 2.8.0 #2483
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
…nto add/api-pull-card-info # Conflicts: # src/API/Site/Controllers/RestAPI/AuthController.php # tests/Unit/API/Site/Controllers/RestAPI/AuthControllerTest.php
API PULL - Add Notices inside GMC Card in Settings
…nto add/block-push-products
…ogle-wpcom-app-in-setting-page
API PULL - Block syncing when notifications are enabled
Release 2.7.7 - Merge `trunk` to `develop`
[API PULL] E2E TESTS for Notifications schedule
…ket.io-parser-3.3.4 Bump socket.io-parser from 3.3.3 to 3.3.4
Google API Project
Rebranding Google Listings and Ads
[API PULL] Adding more tests for Notifications
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## trunk #2483 +/- ##
=========================================
+ Coverage 64.3% 64.5% +0.2%
- Complexity 4281 4564 +283
=========================================
Files 780 795 +15
Lines 21910 22844 +934
Branches 1219 1220 +1
=========================================
+ Hits 14097 14739 +642
- Misses 7646 7938 +292
Partials 167 167
Flags with carried forward coverage won't be shown. Click here to find out more.
|
What's Changed[Add] New Features 🎉
Full Changelog: 2.7.7...2.8.0 |
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
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/
trunk
todevelop
(PR), if applicable for this repo.