Release 2.6.0 #2282
Merged
Release 2.6.0 #2282
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
…` to `AttributesTrait`.
…s in `AttributesForm` as a method.
… Editor for product attributes.
…heritance classes.
…ct\Attributes\Input`.
…e to get the support of the newer WC packages.
…condition_callback` to be null.
…lect-with-text field.
…Admin\ProductBlocksService` class.
…or for channel visibility setup.
…compatibility Product Block Editor: Declare feature compatibility
…ck-editor Product Block Editor: Support the new product editor
…he default charset change in MariaDB v11.3.1. Ref: - https://jira.mariadb.org/browse/MDEV-32975 - WordPress/gutenberg#59237
…ads-accounts 401 handling for connected Ads accounts
Fix the compatibility issue in starting E2E test environment due to the default charset change in MariaDB v11.3.1
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## trunk #2282 +/- ##
=========================================
+ Coverage 59.1% 62.2% +3.2%
- Complexity 4142 4190 +48
=========================================
Files 747 748 +1
Lines 21303 21547 +244
Branches 532 532
=========================================
+ Hits 12580 13406 +826
+ Misses 8272 7690 -582
Partials 451 451
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
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
trunktodevelop(PR), if applicable for this repo.