Bump com.google.gms.google-services from 4.4.4 to 4.5.0

[dependabot]

Bumps com.google.gms.google-services from 4.4.4 to 4.5.0.

[dangermattic]

	1 Warning
⚠️	PR is not assigned to a milestone.

Generated by 🚫 Danger

[wpmobilebot]

Build environment changes

list

! Upgraded Dependencies
com.google.gms.google-services:com.google.gms.google-services.gradle.plugin:4.5.0, (changed from 4.4.4)
com.google.gms:google-services:4.5.0, (changed from 4.4.4)

tree

-\--- com.google.gms.google-services:com.google.gms.google-services.gradle.plugin:4.4.4
-     \--- com.google.gms:google-services:4.4.4
-          +--- com.google.android.gms:strict-version-matcher-plugin:1.2.4
-          |    +--- com.google.code.findbugs:jsr305:3.0.2
-          |    +--- com.google.guava:guava:27.0.1-jre -> 33.5.0-jre (*)
-          |    \--- org.jetbrains.kotlin:kotlin-stdlib-jdk8:1.4.10 -> 2.2.21 (*)
-          +--- com.google.code.gson:gson:2.8.5 -> 2.11.0 (*)
-          \--- org.jetbrains.kotlin:kotlin-stdlib-jdk8:1.7.10 -> 2.2.21 (*)
+\--- com.google.gms.google-services:com.google.gms.google-services.gradle.plugin:4.5.0
+     \--- com.google.gms:google-services:4.5.0
+          +--- com.google.android.gms:strict-version-matcher-plugin:1.2.4
+          |    +--- com.google.code.findbugs:jsr305:3.0.2
+          |    +--- com.google.guava:guava:27.0.1-jre -> 33.5.0-jre (*)
+          |    \--- org.jetbrains.kotlin:kotlin-stdlib-jdk8:1.4.10 -> 2.2.21 (*)
+          +--- com.google.code.gson:gson:2.8.5 -> 2.11.0 (*)
+          \--- org.jetbrains.kotlin:kotlin-stdlib-jdk8:1.7.10 -> 2.2.21 (*)

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack Android by scanning the QR code below to install the corresponding build.

	App Name	Jetpack Android
	Build Type	Debug
	Version	pr22992-65d3e2a
	Build Number	1497
	Application ID	com.jetpack.android.prealpha
	Commit	65d3e2a
	Installation URL	5qfl3do8s0pjo

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress Android by scanning the QR code below to install the corresponding build.

	App Name	WordPress Android
	Build Type	Debug
	Version	pr22992-65d3e2a
	Build Number	1497
	Application ID	org.wordpress.android.prealpha
	Commit	65d3e2a
	Installation URL	4m08cm77eibc8

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[nbradbury]

Holding off on this until release notes are available.

[nbradbury]

Here’s what actually changed between 4.4.4 and 4.5.0.

com.google.gms.google-services 4.4.4 → 4.5.0

The official “release notes” pointer in the repo just redirects to the Firebase Android release notes (Google doesn’t maintain a per-version changelog for this plugin), so the authoritative source is the commit history. Confirmed via google/play-services-plugins: the version bump is commit #424 (2026-05-28), and only one functional change landed in the plugin since 4.4.4:

reCAPTCHA site key support (#423) — The plugin now extracts the recaptcha_site_key field from your google-services.json and emits it into the generated resources.xml (as an Android string resource). This is what consumes the new key that Firebase App Check / reCAPTCHA Enterprise integrations rely on.
Everything else in the gap was non-functional (docs/version housekeeping). Note that broader build-infra work — Gradle 9.0.0 upgrade, Kotlin Gradle Plugin 1.7.22 → 2.1.0, and removal of deprecated config-cache APIs — landed in Sept 2025 under the 4.4.4 line, so it’s already in your current version and not part of this bump.

What this means for WordPress-Android

Impact: effectively zero unless you use reCAPTCHA/App Check. The plugin only emits the recaptcha_site_key resource if that field exists in google-services.json. Your committed file is google-services.json-example (auto-copied at WordPress/build.gradle:570), which won’t contain that key, so the generated resources are unchanged.
No API surface change for how the plugin is applied — the catalog one-liner is the only edit needed.
So my earlier verdict holds: low-risk bump, the only new behavior is opt-in via a google-services.json field you’re not using. Approve pending green CI.

[nbradbury]