Release 2.8.3

[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.3
   git checkout release/2.8.3

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

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

   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.3, 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 72.22222% with 5 lines in your changes missing coverage. Please review.

Project coverage is 64.8%. Comparing base (4cab1dc) to head (efe3084).

Files	Patch %	Lines
js/src/hooks/useUpsertAdsAccount.js	0.0%	3 Missing and 1 partial ⚠️
src/Integration/WPCOMProxy.php	92.9%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             trunk   #2548   +/-   ##
=======================================
  Coverage     64.7%   64.8%           
- Complexity    4580    4585    +5     
=======================================
  Files          801     801           
  Lines        22976   22987   +11     
  Branches      1229    1232    +3     
=======================================
+ Hits         14875   14887   +12     
+ Misses        7934    7932    -2     
- Partials       167     168    +1     

Flag	Coverage Δ
js-unit-tests	63.8% <0.0%> (-<0.1%)	⬇️
php-unit-tests	65.0% <92.9%> (+<0.1%)	⬆️

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

Files	Coverage Δ
src/Integration/WPCOMProxy.php	74.1% <92.9%> (+3.9%)	⬆️
js/src/hooks/useUpsertAdsAccount.js	50.0% <0.0%> (-8.8%)	⬇️

... and 1 file with indirect coverage changes

[jorgemd24]

What's Changed

[Fix] Fixes 🛠

• Set empty props as objects in WPCOM Proxy responses by @puntope in Set empty props as objects in WPCOM Proxy responses #2519

[Tweak] Tweaked 🔧

• Display body message if error status is 406 during account creation by @martynmjones in Display body message if error status is 406 during account creation #2505
• Upgrade readme details by @puntope in Upgrade readme details #2545

[Dev] Developer-facing changes 🧑‍💻

• Make the value entering of the billing state field in e2e test compatible with WC < 9.2 by @eason9487 in Make the value entering of the billing state field in e2e test compatible with WC < 9.2 #2528
• Prevent E2E tests from failing randomly due to getting product block attribute locators before they are rendered by @eason9487 in Prevent E2E tests from failing randomly due to getting product block attribute locators before they are rendered #2546

Full Changelog: 2.8.2...2.8.3