Release 2.8.7

[github-actions]

Checklist

1. Check if the version, base, and target branches are as you desire.
2. Make sure you have woorelease installed and set up.
3. Go to your local repo clone, and check out this PR to be able to commit any potential adjustments.

   git fetch origin release/2.8.7
   git checkout release/2.8.7

4. Remove older changelog entries from readme.txt (keep the last two versions, since we will be adding a third during the release), commit changes.
5. If there are new database migration classes (under src/DB/Migration/), modify their applicable version set in the get_applicable_version class of each migration class to be the same value as the version that is to be released.
   ⚠️ Notice that 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 file Migration20211228T1640692399.php inside src/DB/Migration/, you should open that file and in the method get_applicable_version return 1.12.0.
6. ❗ If this release has updated composer packages, we should test Composer package conflicts with other plugins.
7. Simulate the release locally

   woorelease simulate --product_version=2.8.7  --wp_tested=6.7 --wc_tested=9.4 --generate_changelog https://github.com/woocommerce/google-listings-and-ads/tree/release/2.8.7

   Note: Select y when prompted: "Would you like to add/delete them in the svn working copy?"
8. The changelog is correct.
   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 the changelog: none label.
   You can also edit the changelog manually in the woorelease release step later.
9. Automated tests are passing.
10. Test the package
    1. Install the /tmp/google-listings-and-ads.zip file on a test site
    2. Confirm it activates without warnings/errors and is showing the right versions
    3. Run a few basic smoke tests

Next steps

1. Do the final release

   woorelease release --product_version=2.8.7  --wp_tested=6.7 --wc_tested=9.4  --generate_changelog https://github.com/woocommerce/google-listings-and-ads/tree/release/2.8.7
   

   When prompted for changelog entries, double-check and apply any changes if needed.
2. Confirm the release using the activation link from your email.
   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/
3. Go to https://github.com/woocommerce/google-listings-and-ads/releases/2.8.7, generate GitHub release notes, and paste them as a comment here.
4. Merge this PR after the new release is successfully created and the version tags are updated.
5. Merge trunk to develop (PR), if applicable for this repo.
6. Update documentation
   • Publish any new required docs
   • Update triggers/rules/actions listing pages
7. Mark related ideas complete on the feature requests page.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 64.9%. Comparing base (dffee9c) to head (8267a39).

Additional details and impacted files

@@            Coverage Diff            @@
##             trunk   #2675     +/-   ##
=========================================
+ Coverage     64.7%   64.9%   +0.1%     
  Complexity    4596    4596             
=========================================
  Files          793     793             
  Lines        22970   24342   +1372     
  Branches      1231    1231             
=========================================
+ Hits         14868   15790    +922     
- Misses        7929    8379    +450     
  Partials       173     173             

Flag	Coverage Δ
js-unit-tests	62.7% <ø> (ø)
php-unit-tests	65.4% <ø> (+0.1%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
src/DB/Table/AttributeMappingRulesTable.php	46.7% <ø> (ø)

... and 203 files with indirect coverage changes

[eason9487]

What's Changed

Fixes 🛠

• WordPress 6.7 Compatibility: Avoid block toolbar appearing when interacting custom product blocks by @eason9487 in WordPress 6.7 Compatibility: Avoid block toolbar appearing when interacting custom product blocks #2670
• Remove vendor files that prints php information phpinfo() by @ianlin in Remove vendor files that prints php information phpinfo() #2673

Tweaked 🔧

• WordPress 6.7 Compatibility: Avoid errors in the database where a TEXT type can't have a default value by @eason9487 in WordPress 6.7 Compatibility: Avoid errors in the database where a TEXT type can't have a default value #2667
• WordPress 6.7 Compatibility: Adjust the radio control layout to align well with the extended content by @eason9487 in WordPress 6.7 Compatibility: Adjust the radio control layout to align well with the extended content #2671

Developer-facing changes 🧑‍💻

• WordPress 6.7 Compatibility: Fix the issue that E2E test can't log in to wp-admin by @eason9487 in WordPress 6.7 Compatibility: Fix the issue that E2E test can't log in to wp-admin #2668