Release 1.101.0

[aaemnnosttv]

---

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

[techanvil]

QA ✅

• Smoke tested.
• Verified the changes I’ve been involved with, barring those aspects which are specific to GA4 Reporting, as they will be covered in the forthcoming E2E testing and there would not be time to cover them all in this round of release testing.
• Performed some ad-hoc testing.

[mohitwp]

QA Update ⚠️

• On view only dashboard if AdSense is shared through Dashboard sharing then I'm getting console error.
  Google Site Kit API Error method:GET datapoint:settings type:modules identifier:adsense error:"Sorry, you are not allowed to do that." On latest environment, I'm not getting this console error.

cc @wpdarren

[aaemnnosttv]

@wpdarren I just tested this and those are both showing for me on the shared dashboard. The problem in your case is that Search Console isn't shared with your user's role as can be seen in the view only menu

[wpdarren]

@aaemnnosttv yes, I just deleted my comment because I realised I was being stupid. 🤣

[wpdarren]

QA Update: ✅

Note: I am able to see the console error that Mohit highlighted above.

I have completed my release testing:

• Went through our QA checklist on a site in gathering, zero data state, and real data.
• Didn't complete any GA4 Reporting testing as this will be picked up next week in our final E2E testing.
• Completed additional testing around AdSense with legacy and V2.
• Tested dashboardSharing and ga4ActivationBanner
• Made sure that GTESupport was still functioning as expected.

[aaemnnosttv]

I just opened #7064 as a quick fix for something that I noticed while testing. It's not a regression but something we should include in the release which is a very small change that won't invalidate the rest of the QA done here.

[hussain-t]

QA Verified ✅

• Smoke tested.
• Verified the changes I’ve been involved with.
• Performed some ad-hoc testing.

[nfmohit]

Release Tested ✅

• Release tested 1.101.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 our release testing checklist to ensure everything is checked.

[tofumatt]

QA ✅

• Spent time testing with GA4 Reporting disabled and enabled.
• Tested GA4 Reporting on mobile viewports.
• Usual smoke and setup flow tests.

Spent a bit more time with this one since it's a big release and we haven't done a release in awhile.

Everything looked good for me. 👍🏻

[jimmymadon]

QA Verified ✅

• Smoke tested and verified the changes I’ve been involved with.

[10upsimon]

Release Tested ✅

• Release tested 1.101.0 of the plugin on InstaWP site and configured from a fresh installation
• Smoke tested admin/settings views
• Smoke tested frontend/UI, no unexpected errors appeared to be present
• Very high level verification of changes as obtained via the approved/merged issues of the release
• Performed testing steps as per release testing check list

[kuasha420]

QA: ✔️

• Went through the release QA testing, set everything up from scratch on a fresh site.
• Tested with and without gteSupport and dashboardSharing feature flag.
• Tested the changes I was involved with.

LGTM. 👍

[mohitwp]

@aaemnnosttv Just flagging here the issue which I reported above. Wondering if it requires fix or not ?

[aaemnnosttv]

@mohitwp thanks for flagging, I'm double-checking this now.

[aaemnnosttv]

The issue regarding the console error on the view only dashboard is due to the AdSense status migration checks added in #5628 which haven't been made conditionally on the view-only dashboard. We'll want to address that in a follow-up but it need not block the release since the error does not break anything, and a non-admin shouldn't see that migration notice anyways since they wouldn't be able to action it for the same reason.

I'll open an issue to address this, thanks again for flagging 👍

Edit: Opened #7074