Release 2.8.5

[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.5
   git checkout release/2.8.5

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.5  --wc_tested=9.3.0 --generate_changelog https://github.com/woocommerce/google-listings-and-ads/tree/release/2.8.5

   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.5  --wc_tested=9.3.0  --generate_changelog https://github.com/woocommerce/google-listings-and-ads/tree/release/2.8.5
   

   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.5, 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

Attention: Patch coverage is 52.00000% with 24 lines in your changes missing coverage. Please review.

Project coverage is 64.7%. Comparing base (aeb4245) to head (8ce5aef).

Files with missing lines	Patch %	Lines
src/MerchantCenter/AccountService.php	54.2%	11 Missing ⚠️
src/Menu/Dashboard.php	0.0%	5 Missing ⚠️
src/Menu/GetStarted.php	0.0%	5 Missing ⚠️
src/ConnectionTest.php	0.0%	2 Missing ⚠️
...ernal/DependencyManagement/CoreServiceProvider.php	0.0%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff            @@
##             trunk   #2586     +/-   ##
=========================================
+ Coverage     64.5%   64.7%   +0.2%     
- Complexity    4591    4596      +5     
=========================================
  Files          796     793      -3     
  Lines        22992   22967     -25     
  Branches      1234    1231      -3     
=========================================
+ Hits         14837   14865     +28     
+ Misses        7982    7929     -53     
  Partials       173     173             

Flag	Coverage Δ
js-unit-tests	62.7% <100.0%> (-0.1%)	⬇️
php-unit-tests	65.3% <47.8%> (+0.3%)	⬆️

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

Files with missing lines	Coverage Δ
js/src/attribute-mapping/index.js	100.0% <ø> (ø)
js/src/components/main-tab-nav/main-tab-nav.js	90.0% <100.0%> (ø)
js/src/dashboard/index.js	78.1% <ø> (ø)
js/src/hooks/useLayout.js	9.1% <ø> (ø)
js/src/hooks/useMenuEffect.js	100.0% <100.0%> (ø)
js/src/index.js	77.1% <100.0%> (-2.3%)	⬇️
js/src/product-feed/index.js	100.0% <ø> (ø)
src/API/WP/NotificationsService.php	95.2% <100.0%> (+0.1%)	⬆️
src/Assets/BaseAsset.php	75.7% <100.0%> (+18.4%)	⬆️
src/Settings/SyncerHooks.php	100.0% <100.0%> (ø)
... and 6 more

... and 2 files with indirect coverage changes

[martynmjones]

What's Changed

[Breaking] Breaking Changes 🚨

• Remove Woo Navigation integration by @tomalec in Remove Woo Navigation integration #2574

[Fix] Fixes 🛠

• Fix issue with syncing shipping rates with more than two decimals by @jorgemd24 in Fix issue with syncing shipping rates with more than two decimals #2573
• Log Exception if an asset is enqueued before being registered by @martynmjones in Log Exception if an asset is enqueued before being registered #2576

[Tweak] Tweaked 🔧

• Use remote-site-status to check the WPCOM Auth status by @puntope in Use remote-site-status to check the WPCOM Auth status #2547

Full Changelog: 2.8.4...2.8.5