Release 1.136.0

[tofumatt]

---

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

• Release is prepared, tested, and deployed to wordpress.org.

Implementation Brief

• N/A

QA Brief

• N/A

Changelog entry

• N/A

[wpdarren]

QA Update: ⚠️

Update: @techanvil found a regression in this ticket and it has been sent back to Execution for a fix.

I’ve found a regression. Its not user-facing, but we might want to take a look at it. On the main branch (doesn’t occur on 1.135.0) — when I go to Site Kit settings an error occurs in the console.

GET 404 (Not Found) Google Site Kit API Error method:GET datapoint:audience-settings type:core identifier:user error:"No route was found matching the URL and request method."

It appears to be related to Audience Segmentation. No feature flags are enabled. It’s a new website.

[wpdarren]

QA Update: ✅

I went through our usual QA checks:

• Tested on a site in gathering and zero data state
• Tested on a site with live data
• Tested Dashboard sharing
• Tested Ad Blocking Recovery
• Tested Enhanced Measurement
• Tested User Input and KMW widget
• Tested Consent Mode
• Tested the Ads Module
• Tested ICEI

The issue above is with @ankitrox for a PR on 9264.

Notes: I didn't notice any banner notification issues but have asked @mohitwp to go through the testing document for this epic since Phase 1 is finalised. In addition, I haven't included any testing on Reader Revenue Manager, but Mohit and Kelvin are picking this up -- I will spend some time on Monday running through the testing.

[tofumatt]

QA ✅

• Smoke tested setup, disconnection, module connections, etc.
• Tested Dashboard Sharing
• Tested Screen Reader functionality
• Tested changes in release
• Paid particular attention to banner notifications/other notifications.

All looks good to me 👍🏻

[hussain-t]

QA Verified :white_check_mark:

• Smoke tested.
• Verified the changes I’ve been involved with.
• Tested Dashboard sharing
• Tested Ad Blocking Recovery
• Tested Consent Mode
• Tested AdSense+GA4 Integration
• Tested the Ads Module
• Tested ICEI
• Performed some ad-hoc testing.

LGTM :+1:

[nfmohit]

Release Tested ✅

• Release tested 1.136.0 thoroughly.
• Set everything up from scratch on a live (InstaWP) site.
• Didn't spot any unexpected console errors.
• Verified UI in different device breakpoints.
• Verified changes I've been involved with.
• Used the release testing checklist to ensure everything was checked.
• Tested RRM.
• Tested Dashboard Sharing.
• Tested Ad Blocking Recovery.
• Tested Consent Mode.
• Tested Ads module.
• Tested KMW.
• Tested ICEI.
• Tested Enhanced Measurement.

[mohitwp]

QA Update ✅

• Ran QA check list.
• Verified SK setup without Analytics.
• Verified SK setup with Analytics.
• Verified AdSense, Ads module, Tag manager setup.
• Tested banner notifications.
• Verified Conversion reporting.
• Verified main, entity and view only dashboard.
• Note : I'm working on RRM final e2e QA.

[jimmymadon]

Release Testing ✅

• Went through the release testing check list.
• Tested Ads and PAX setup flows.
• Tested all refactored notifications so far.

[zutigrm]

QA ✅

• Tested available modules
• Tested issues I was involved with
• Tested Key metrics
• Tested dashboard sharing and entity dashboard
• Tested Ads module
• Smoke tested

LGTM

[mohitwp]

QA Update ⚠️

• I completed final testing of RRM.
• Issue >I noticed that the RRM prompt appears in the front end even after we disconnect the RRM module.

cc @nfmohit @wpdarren

[mohitwp]

QA Update ✅

• I completed final testing of RRM.
• Above issue was due to code snippet plugin. I disconnected the plugin and prompt working as expected.