-
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.6.5 #2347
Merged
Merged
Release 2.6.5 #2347
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
Release 2.6.4 - Merge `trunk` to `develop`
Bumps [express](https://github.com/expressjs/express) from 4.18.2 to 4.19.2. - [Release notes](https://github.com/expressjs/express/releases) - [Changelog](https://github.com/expressjs/express/blob/master/History.md) - [Commits](expressjs/express@4.18.2...4.19.2) --- updated-dependencies: - dependency-name: express dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
Update test proxy port
…ress-4.19.2 Bump express from 4.18.2 to 4.19.2
…and-conversions Adjust Review Clicks and Ads Conversions Metrics threshold for Inbox Notes
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## trunk #2347 +/- ##
=========================================
+ Coverage 62.7% 62.9% +0.1%
Complexity 4252 4252
=========================================
Files 751 751
Lines 21789 21783 -6
Branches 542 542
=========================================
+ Hits 13672 13700 +28
+ Misses 7661 7627 -34
Partials 456 456
Flags with carried forward coverage won't be shown. Click here to find out more.
|
[Dev] Developer-facing changes 🧑💻
[Tweak] Tweaked 🔧
|
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
(PR), if applicable for this repo.