Release 2.9.4

[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.9.4
   git checkout release/2.9.4

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.9.4  --generate_changelog https://github.com/woocommerce/google-listings-and-ads/tree/release/2.9.4

   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.9.4   --generate_changelog https://github.com/woocommerce/google-listings-and-ads/tree/release/2.9.4
   

   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.9.4, 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 92.85714% with 2 lines in your changes missing coverage. Please review.

Project coverage is 66.3%. Comparing base (adf9a6d) to head (e7b5d92).

Files with missing lines	Patch %	Lines
src/API/Google/Query/AdsQuery.php	88.9%	1 Missing ⚠️
...ernal/DependencyManagement/CoreServiceProvider.php	0.0%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             trunk   #2744   +/-   ##
=======================================
  Coverage     66.3%   66.3%           
+ Complexity    4693    4690    -3     
=======================================
  Files          816     816           
  Lines        24805   24794   -11     
  Branches      1273    1273           
=======================================
+ Hits         16435   16440    +5     
+ Misses        8197    8181   -16     
  Partials       173     173           

Flag	Coverage Δ
js-unit-tests	63.5% <ø> (ø)
php-unit-tests	67.0% <92.9%> (+0.1%)	⬆️

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

Files with missing lines	Coverage Δ
.../free-listings/setup-free-listings/form-content.js	5.9% <ø> (ø)
...nts/shipping-rate-section/shipping-rate-section.js	100.0% <ø> (ø)
js/src/hooks/useSettings.js	25.0% <ø> (ø)
js/src/pages/edit-free-listings/index.js	2.0% <ø> (ø)
...es/onboarding/setup-stepper/saved-setup-stepper.js	87.2% <ø> (ø)
js/src/pages/settings/setup-tax-rate/tax-rate.js	33.3% <ø> (ø)
...pages/settings/setup-tax-rate/useDisplayTaxRate.js	100.0% <ø> (ø)
src/API/Google/Ads.php	100.0% <ø> (+11.3%)	⬆️
src/API/Google/AdsAsset.php	95.2% <ø> (ø)
src/API/Google/AdsAssetGroup.php	83.3% <100.0%> (+0.1%)	⬆️
... and 20 more

... and 1 file with indirect coverage changes

[tomalec]

QIT activation, security, api and E2E (except of known false negatives) are passing
https://github.com/woocommerce/google-listings-and-ads/actions/runs/12485668277

[tomalec]

• Fix - Clear previous errors after completing sync.
• Tweak - Adjust conditions for MCM.
• Update - Google Ads API to v18.

What's Changed

[Update] Updated ✨

• Update Google Ads API to v18 by @mikkamp in Update Google Ads API to v18 #2740

[Fix] Fixes 🛠

• Adjust conditions for MCM by @mikkamp in Adjust conditions for MCM #2739
• Clear previous errors after completing sync by @mikkamp in Clear previous errors after completing sync #2738

[Dev] Developer-facing changes 🧑‍💻

• Move the shared files for the tax rate settings by @eason9487 in Move the shared files for the tax rate settings #2741

Full Changelog: 2.9.3...2.9.4