Bringing inline threading to direct messages in Google Chat

What’s changing

We’re excited to announce that inline threading is rolling out for direct messages (DMs) and group direct messages (gDMs) in Google Chat. This has been a highly requested feature, and we're pleased to deliver it as part of our effort to simplify the Chat experience and address top user feedback about conversation consistency.

Until now, inline threading was only available in Spaces. With this update, you can now reply in-thread to any message in a direct conversation, just as you do in a Space. This helps to keep conversations organized, allowing you and your colleagues to follow specific topics and avoid cluttering the main chat stream.

Getting started

  • Admins: There is no admin control for this feature.
  • End users: There is no end user setting for this feature. This feature will be ON by default as it rolls out.

Rollout pace

Availability

Available to all Google Workspace customers, Workspace Individual Subscribers, and users with personal Google accounts

Resources

Chrome for Android

  Hi, everyone! We've just released Chrome 142 (142.0.7444.138) 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 releases (Windows: 142.0.7444.134/.135,  Mac: 142.0.7444.134, Linux: 1142.0.7444.134)) unless otherwise noted.


Krishna Govind
Google Chrome

Chrome for Android

  Hi, everyone! We've just released Chrome 142 (142.0.7444.138) 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 releases (Windows: 142.0.7444.134/.135,  Mac: 142.0.7444.134, Linux: 1142.0.7444.134)) unless otherwise noted.


Krishna Govind
Google Chrome

Set sharing expirations on files and folders in shared drives

What’s changing

We previously introduced the option to set expirations on files that reside in shared drives using the Google Drive API. Today, we are bringing the ability to set expiring access for files and folders in shared drives directly from the sharing dialog. This highly-requested feature brings the ease and security of My Drive access controls into your collaborative shared drives.

File expirations

You can now set expirations when sharing files in a shared drive. This lets you add an expiration date right in the sharing dialog for temporary collaborators, ensuring access is automatically revoked and eliminating the need for manual cleanup.
Add expiration while sharing files in shared drives.

Add expiration while sharing files in shared drives.

Folder expirations

For shared drive folders, you can now apply an expiration date specifically to the Viewer role. This setting is easily accessible in the folder's sharing dialog, helping you automatically remove read-only access when a collaborator's temporary need is finished.
Add expiration for Viewer role while sharing folders in shared drives.

Consistent expiration behavior in My Drive

We're standardizing access expiration for files and folders in My Drive. The experience is now consistent with shared drives, making it more predictable for you to know when access will expire.

Old behavior: If you granted someone temporary Editor access to a file inside a parent folder they could only view, they would lose all access to the file once their Editor permission expired.

New behavior: When their temporary Editor access expires, their permission will revert to the access they have on the parent folder (in this case, Viewer). They will not lose access to the file completely.

Editor access expires, and reverts to Viewer access (user has Viewer access on the parent folder).
Editor access expires, and reverts to Viewer access (user has Viewer access on the parent folder).

Getting started

You can only set sharing expirations on Web and Android phones. Expirations cannot be set on iOS devices in My Drive or shared drives.

Rollout pace

Availability

Available to Google Workspace:

  • Business Starter, Standard, Plus
  • Enterprise Starter, Standard, Plus
  • Enterprise Essentials, Enterprise Essentials Plus
  • Education Standard, Plus
  • Nonprofits
  • Frontline Starter, Standard, Plus
Also available to:
  • Google One AI Premium 
  • Google AI Pro and Ultra
  • Gemini Business, Enterprise*
*As of January 15, 2025, we’re no longer offering the Gemini Business and Gemini Enterprise add-ons for sale. Please refer to this announcement for more details. 

Resources


Stable Channel Update for Desktop

The Stable channel has been updated to 142.0.7444.134/.135 for Windows and 142.0.7444.135 for Mac and 142.0.7444.134 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 5 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.





[TBD][443906252] High CVE-2025-12725: Out of bounds write in WebGPU. Reported by Anonymous on 2025-09-09

[TBD][447172715] High CVE-2025-12726: Inappropriate implementation in Views. Reported by Alesandro Ortiz on 2025-09-25

[TBD][454485895] High CVE-2025-12727: Inappropriate implementation in V8. Reported by 303f06e3 on 2025-10-23

[TBD][452392032] Medium CVE-2025-12728: Inappropriate implementation in Omnibox. Reported by Hafiizh on 2025-10-16

[TBD][454354281] Medium CVE-2025-12729: Inappropriate implementation in Omnibox. Reported by Khalil Zhani on 2025-10-23




We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.

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.


Srinivas Sista
Google Chrome