Extended Stable Updates for Desktop

 The Extended Stable channel has been updated to 138.0.7204.97 for Windows and 138.0.7204.93 Mac which will roll out over the coming days/weeks.

A full list of changes in this build is available in the log. Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Krishna Govind
Google Chrome

Chrome for Android Update

 Hi, everyone! We've just released Chrome 138 (138.0.7204.63) for Android. It'll become available on Google Play over the next few days. 

This release includes stability and performance improvements. You can see a full list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.


Android releases contain the same security fixes as their corresponding Desktop (Windows: 138.0.7204.96/97, Mac:138.0.7204.92/93 and Linux: 138.0.7204.96) unless otherwise noted.


Krishna Govind
Google Chrome

Chrome for Android Update

 Hi, everyone! We've just released Chrome 138 (138.0.7204.63) for Android. It'll become available on Google Play over the next few days. 

This release includes stability and performance improvements. You can see a full list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.


Android releases contain the same security fixes as their corresponding Desktop (Windows: 138.0.7204.96/97, Mac:138.0.7204.92/93 and Linux: 138.0.7204.96) unless otherwise noted.


Krishna Govind
Google Chrome

Stable Channel Update for Desktop

The Stable channel has been updated to 138.0.7204.96/.97 for Windows, 138.0.7204.92/.93 for Mac and 138.0.7204.96 for Linux which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log.


 Security Fixes and Rewards

Note: Access to bug details and links may be kept restricted

until a majority of users are updated with a fix. We will also retain

restrictions if the bug exists in a third party library that other projects

similarly depend on, but haven’t yet fixed.


This update includes 1 security fix.

Below, we highlight fixes that were contributed by external researchers.

Please see the Chrome Security Page for more information.


[NA][427663123] High CVE-2025-6554: Type Confusion in V8.

Reported by Clément Lecigne of Google's Threat Analysis Group on 2025-06-25.

This issue was mitigated on 2025-06-26 by a configuration change

pushed out to Stable channel across all platforms.


Google is aware that an exploit for CVE-2025-6554 exists in the wild.


Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.


Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.


Krishna Govind
Google Chrome

Now generally available: prevent sensitive changes by locking Google Groups

What’s changing 

We’re pleased to announce the ability to label a Google Group as “Locked” is now generally available. When a group is “locked”, it heavily restricts the ability to change group attributes, such as the group name & email address) and memberships. 

This is helpful when admins need to sync their groups from an external source and want to prevent things from getting out of sync or want to restrict changes to sensitive groups in general.

The Group Details page in the Admin console shows a “Locked” label on the group, with the message “You can’t update this group - it might be managed by an external identity system.”


Who’s impacted

Admins

Why it’s important

If you use third-party tools, like Entra ID, to manage group synchronization, you may encounter inconsistencies when modifications are made to these groups, like adding or removing members, for example. To help address this, we’re introducing the option to “lock” a group, which will prevent modifications within Google Workspace and help maintain synchronization with the external source. 

When a group is locked, only certain admins* can modify:
  • The group name, description, email, and alias(es)
  • Group labels
  • Memberships (adding or removing members) and member restrictions
  • Membership roles
  • Delete the group
  • Set up a new membership expiry

When a group is locked, access and content moderation settings are not affected, this includes:
  • Who can post
  • Who can view members
  • Who can contact members
  • Membership removals due to an existing membership expiry
  • Access or content moderation settings

*Super Admins, Group Admins, and Group Editors with a condition that includes “Locked Groups”

Additional details

By default, the changes listed above will be restricted from end users, including group owners and managers of a locked group. If you want to also restrict some admins from making these changes in the Admin Console or APIs, you can assign them the Group Editor role with a condition that excludes locked groups. 

The ability to lock or unlock a group using the “Locked” label is available to Super Admins, Group Admins, or a custom role with the “Manage Locked Label” privilege. Lock a group using the “Locked” group label in the Admin Console, or the Cloud Identity Groups API.

Getting started


Rollout pace


Availability

Available for Google Workspace:
  • Enterprise Standard and Plus
  • Enterprise Essentials Plus
  • Education Standard and Plus
  • Also available to Cloud Identity Premium customers

Resources


Hardware Key Certificate Management for client-side encryption in Gmail

What’s changing 

Gmail now allows users with hardware keys, such as PIV/CAC smartcards, to directly manage their digital signature and encryption certificates within Gmail settings. Prior to this update, admins needed to upload encryption keys for their users – now users can configure their own keys in Gmail, without needing an admin. 

Gmail > Settings > Accounts > Encryption certificates

Additional details 

While Workspace encrypts data at rest and in transit by using secure-by-design cryptographic libraries, client-side encryption ensures that you have sole control over encryption keys and access to your data. Client-side encryption ensures sensitive data in the email body and attachments are indecipherable to Google servers — you retain control over encryption keys and the identity service to access those keys. For more information, check out our original announcement and the Workspace blog. 

Getting started 

  • Admins: In order for your users to add certificates from a hardware key, you must first enable and install the Workspace Hardware Keys application to user machines. 
  • End users: Visit the Help Center to learn more about using hardware keys for encryption. 

Rollout pace 


Availability 


Resources 

[Update] Add Conversion Environment to Google Ads Conversion Imports

Previously we announced that, starting on June 30, 2025, in-app conversions imported through the Google Ads API must include a value for the ClickConversion.conversion_environment field. The timing and details for this rollout have changed.

Now, starting September 30, 2025, we will begin gradually rolling out a change to our bidding models so that they will start using the presence of the ClickConversion.conversion_environment field in imported in-app conversions to ensure accurate attribution for smarter bidding and optimal campaign performance. This means that if you are using the Google Ads API to measure in-app conversions, your campaign performance may degrade if the ClickConversion.conversion_environment field is not set.

For developers importing in-app conversions, the following considerations still apply:

  1. In-app conversions are defined as any conversion events that occur within an app, such as purchase, add to cart, or sign up.
  2. Once this bidding model change is launched to a campaign, if you do not include the conversion_environment field when importing conversions, you may observe fewer in-app conversions and worse overall campaign performance.
  3. If you do include conversion_environment data for your imported conversions, it ensures attribution accuracy and campaign effectiveness.
  4. The presence or absence of the conversion_environment parameter does not impact conversion uploads. These conversions will still be consumed and reported, with no error messages.

If you have any questions or need help, see the Google Ads API support page for options.

- Ben Karl, on behalf of the Google Ads API Team

Top announcements to know from Google Play at I/O ‘25

Posted by Raghavendra Hareesh Pottamsetty – Google Play Developer and Monetization Lead

At Google Play, we're dedicated to helping people discover experiences they'll love, while empowering developers like you to bring your ideas to life and build successful businesses. This year, Google I/O was packed with exciting announcements designed to do just that. For a comprehensive overview of everything we shared, be sure to check out our blog post recapping What's new in Google Play.

Today, we'll dive specifically into the latest updates designed to help you streamline your subscriptions offerings and maximize your revenue on Play. Get a quick overview of these updates in our video below, or read on for more details.

#1: Subscriptions with add-ons: Streamlining subscriptions for you and your users

We're excited to announce multi-product checkout for subscriptions, a new feature designed to streamline your purchase flow and offer a more unified experience for both you and your users. This enhancement allows you to sell subscription add-ons right alongside your base subscriptions, all while maintaining a single, aligned payment schedule.

The result? A simplified user experience with just one price and one transaction, giving you more control over how your subscribers upgrade, downgrade, or manage their add-ons. Learn more about how to create add-ons.

base subscriptions and add-ons together in a single, streamlined transaction on Google Play
You can now sell base subscriptions and add-ons together in a single, streamlined transaction

#2: Showcasing benefits in more places across Play: Increasing visibility and value

We're also making it easier for you to retain more of your subscribers by showcasing subscription benefits in more key areas across Play. This includes the Subscriptions Center, within reminder emails, and even during the purchase and cancellation processes. This increased visibility has already proved effective, reducing voluntary churn by 2%. To take advantage of this powerful new capability, be sure to enter your subscription benefits details in Play Console.

value notifications across subscriptions center, email reminders, and during purchase transactions, shown across form factors on Google Play
To help reduce voluntary churn, we’re showcasing your subscriptions benefits across Play

#3: New grace period and account hold duration: Decreasing involuntary churn

Another way we’re helping you maximize your revenue is by extending grace periods and account hold durations to tackle unintended subscription losses, which often occur when payment methods unexpectedly decline.

Now, you can customize both the grace period (when users retain access while renewal is attempted) and the account hold period (when access is suspended). You can set a grace period of up to 30 days and an account hold period of up to 60 days. However, the total combined recovery period (grace period + account hold) cannot exceed 60 days.

This means instead of an immediate cancellation, your users have a longer window to update their payment information. Developers who've already extended their decline recovery period—from 30 to 60 days—have seen impressive results, with an average 10% reduction in involuntary churn for renewals. Ready to see these results for yourself? Adjust your grace period and account hold durations in Play Console today.

a ten percent reduction in involuntary churn on Google Play according to internal Google data
Developers who extend their decline recovery period see an average 10% reduction in involuntary churn

But that’s not all. We’re constantly investing in ways to help you optimize conversion throughout the entire buyer lifecycle. This includes boosting purchase-readiness by prompting users to set up payment methods and verification right from device setup, and we've integrated these prompts into highly visible areas like the Play and Google account menus. Beyond that, we're continuously enabling payments in more markets and expanding payment options. Our AI models are even working to optimize in-app transactions by suggesting the right payment method at the right time, and we're bringing buyers back with effective cart abandonment reminders.

That’s it for our top announcements from Google I/O 2025, but there’s so many more updates to discover from this year’s event. Check out What's new in Google Play to learn more, and to dive deeper into the session details, view the Google Play I/O playlist for all the announcements.



Google Play logo

Top announcements to know from Google Play at I/O ‘25

Posted by Raghavendra Hareesh Pottamsetty – Google Play Developer and Monetization Lead

At Google Play, we're dedicated to helping people discover experiences they'll love, while empowering developers like you to bring your ideas to life and build successful businesses. This year, Google I/O was packed with exciting announcements designed to do just that. For a comprehensive overview of everything we shared, be sure to check out our blog post recapping What's new in Google Play.

Today, we'll dive specifically into the latest updates designed to help you streamline your subscriptions offerings and maximize your revenue on Play. Get a quick overview of these updates in our video below, or read on for more details.

#1: Subscriptions with add-ons: Streamlining subscriptions for you and your users

We're excited to announce multi-product checkout for subscriptions, a new feature designed to streamline your purchase flow and offer a more unified experience for both you and your users. This enhancement allows you to sell subscription add-ons right alongside your base subscriptions, all while maintaining a single, aligned payment schedule.

The result? A simplified user experience with just one price and one transaction, giving you more control over how your subscribers upgrade, downgrade, or manage their add-ons. Learn more about how to create add-ons.

base subscriptions and add-ons together in a single, streamlined transaction on Google Play
You can now sell base subscriptions and add-ons together in a single, streamlined transaction

#2: Showcasing benefits in more places across Play: Increasing visibility and value

We're also making it easier for you to retain more of your subscribers by showcasing subscription benefits in more key areas across Play. This includes the Subscriptions Center, within reminder emails, and even during the purchase and cancellation processes. This increased visibility has already proved effective, reducing voluntary churn by 2%. To take advantage of this powerful new capability, be sure to enter your subscription benefits details in Play Console.

value notifications across subscriptions center, email reminders, and during purchase transactions, shown across form factors on Google Play
To help reduce voluntary churn, we’re showcasing your subscriptions benefits across Play

#3: New grace period and account hold duration: Decreasing involuntary churn

Another way we’re helping you maximize your revenue is by extending grace periods and account hold durations to tackle unintended subscription losses, which often occur when payment methods unexpectedly decline.

Now, you can customize both the grace period (when users retain access while renewal is attempted) and the account hold period (when access is suspended). You can set a grace period of up to 30 days and an account hold period of up to 60 days. However, the total combined recovery period (grace period + account hold) cannot exceed 60 days.

This means instead of an immediate cancellation, your users have a longer window to update their payment information. Developers who've already extended their decline recovery period—from 30 to 60 days—have seen impressive results, with an average 10% reduction in involuntary churn for renewals. Ready to see these results for yourself? Adjust your grace period and account hold durations in Play Console today.

a ten percent reduction in involuntary churn on Google Play according to internal Google data
Developers who extend their decline recovery period see an average 10% reduction in involuntary churn

But that’s not all. We’re constantly investing in ways to help you optimize conversion throughout the entire buyer lifecycle. This includes boosting purchase-readiness by prompting users to set up payment methods and verification right from device setup, and we've integrated these prompts into highly visible areas like the Play and Google account menus. Beyond that, we're continuously enabling payments in more markets and expanding payment options. Our AI models are even working to optimize in-app transactions by suggesting the right payment method at the right time, and we're bringing buyers back with effective cart abandonment reminders.

That’s it for our top announcements from Google I/O 2025, but there’s so many more updates to discover from this year’s event. Check out What's new in Google Play to learn more, and to dive deeper into the session details, view the Google Play I/O playlist for all the announcements.



Google Play logo