Google Products (20)
All Google Release Notes (862)
- Jan 20, 2026
- Parsed from source:Jan 20, 2026
- Detected by Releasebot:Jan 20, 2026
- Jan 19, 2026
- Parsed from source:Jan 19, 2026
- Detected by Releasebot:Jan 19, 2026
Gemini CLI by Google
Release v0.24.4
What's Changed
- fix(patch): cherry-pick 88f1ec8 to release/v0.24.0-pr-16179 [CONFLICTS] by @gemini-cli-robot in #16783
Full Changelog: v0.24.0...v0.24.4
Original source Report a problem - Jan 19, 2026
- Parsed from source:Jan 19, 2026
- Detected by Releasebot:Nov 4, 2025
- Modified by Releasebot:Jan 21, 2026
January 19, 2026
SDK Releases
The Firebase SDK for Flutter (v4.8.0) is now available. This release includes changes in Firebase AI Logic, and bug fixes in several products.
Original source Report a problem - Jan 16, 2026
- Parsed from source:Jan 16, 2026
- Detected by Releasebot:Jan 17, 2026
Google Workspace Updates Weekly Recap - January 16, 2026
Workspace Updates this week adds Google Forms close date and response limits, Veo 3.1 supports portrait clips, mobile Meet gets automatic room check‑in, SecOps data connector expands to Education Plus and Standard, and you can edit password‑protected Office files directly in Drive.
A summary of announcements from the last week
The announcements below were published on the Workspace Updates blog over the last week. Please refer to the original blog posts for complete details.
Set Google Forms to automatically stop accepting responses based on date and time or response count
Last year, we introduced a feature that gives Google Forms creators more control over who can respond to their forms via sharing settings. We are now improving how you can choose to manage responses in Google Forms by enabling you to set a close date or response limit for new responses. | Learn more about setting Google Forms to automatically stop accepting responses based on date and time or response count.
Ingredients to Video in Veo 3.1 now supports portrait-sized clips in Google Vids
Today we’re announcing improvements to Veo 3.1 that allow you to generate portrait-sized clips with faster pace and engaging shots, all while delivering realistic audio and maintaining consistency of objects, characters, and backgrounds. | Learn more about Ingredients to Video in Veo 3.1. It now supports portrait-sized clips in Google Vids.
Automatic room check-in for Google Meet available on mobile devices
Mobile Companion Mode now supports automatic room check-in. Using ultrasound detection, your device pairs with room hardware to join meetings instantly, streamlining the process. | Learn more about Automatic room check-in for Google Meet available on mobile devices.
SecOps data connector now available for Google Workspace for Education Plus and Standard
We’re expanding the availability of the Google Workspace SecOps data connector to customers using Google Workspace for Education Plus and Education Standard. This feature was previously only available for our Enterprise customers. | Learn more about the SecOps data connector, now available for Google Workspace for Education Plus and Standard.
Editing password-protected Microsoft Office files directly in Google Drive
We're excited to announce a major improvement to Microsoft Office interoperability in Google Workspace: you can now edit Microsoft Office files that are password-protected, directly within Docs, Sheets, and Slides. | Learn more about editing password-protected Microsoft Office files directly in Google Drive.
Original source Report a problem - Jan 15, 2026
- Parsed from source:Jan 15, 2026
- Detected by Releasebot:Jan 16, 2026
[security] Go 1.25.6 and Go 1.24.12 are released
Go releases 1.25.6 and 1.24.12 fix six security flaws across archive/zip, net/http, crypto/tls, and the Go toolchain, addressing DoS, memory exhaustion, and code execution risks. Upgrading is recommended to stay protected and secure.
Hello gophers,
We have just released Go versions 1.25.6 and 1.24.12, minor point releases.
These releases include 6 security fixes following the security policy :
Security fixes
archive/zip: denial of service when parsing arbitrary ZIP archives
archive/zip used a super-linear file name indexing algorithm that is invoked the first time a file in an archive is opened. This can lead to a denial of service when consuming a maliciously constructed ZIP archive.
Thanks to Thanks to Jakub Ciolek for reporting this issue.
This is CVE-2025-61728 and Go issue https://go.dev/issue/77102 .net/http: memory exhaustion in Request.ParseForm
When parsing a URL-encoded form net/http may allocate an unexpected amount of
memory when provided a large number of key-value pairs. This can result in a
denial of service due to memory exhaustion.
Thanks to jub0bs for reporting this issue.
This is CVE-2025-61726 and Go issue https://go.dev/issue/77101 .crypto/tls: Config.Clone copies automatically generated session ticket keys, session resumption does not account for the expiration of full certificate chain
The Config.Clone methods allows cloning a Config which has already been passed
to a TLS function, allowing it to be mutated and reused.
If Config.SessionTicketKey has not been set, and Config.SetSessionTicketKeys has
not been called, crypto/tls will generate random session ticket keys and
automatically rotate them. Config.Clone would copy these automatically generated
keys into the returned Config, meaning that the two Configs would share session
ticket keys, allowing sessions created using one Config could be used to resume
sessions with the other Config. This can allow clients to resume sessions even
though the Config may be configured such that they should not be able to do so.
Config.Clone no longer copies the automatically generated session ticket keys.
Config.Clone still copies keys which are explicitly provided, either by setting
Config.SessionTicketKey or by calling Config.SetSessionTicketKeys.
This issue was discoverd by the Go Security team while investigating another
issue reported by Coia Prant (github.com/rbqvq).
Additionally, on the server side only the expiration of the leaf certificate, if
one was provided during the initial handshake, was checked when considering if a
session could be resumed. This allowed sessions to be resumed if an intermediate
or root certificate in the chain had expired.
Session resumption now takes into account of the full chain when determining if
the session can be resumed.
Thanks to Coia Prant (github.com/rbqvq) for reporting this issue.
This is CVE-2025-68121 and Go issue https://go.dev/issue/77113 .cmd/go: bypass of flag sanitization can lead to arbitrary code execution
Usage of 'CgoPkgConfig' allowed execution of the pkg-config
binary with flags that are not explicitly safe-listed.
To prevent this behavior, compiler flags resulting from usage
of 'CgoPkgConfig' are sanitized prior to invoking pkg-config.
Thank you to RyotaK (https://ryotak.net) of GMO Flatt Security Inc.
for reporting this issue.
This is CVE-2025-61731 and go.dev/issue/77100 .cmd/go: unexpected code execution when invoking toolchain
The Go toolchain supports multiple VCS which are used retrieving modules and
embedding build information into binaries.
On systems with Mercurial installed (hg) downloading modules (e.g. via go get or
go mod download) from non-standard sources (e.g. custom domains) can cause
unexpected code execution due to how external VCS commands are constructed.
On systems with Git installed, downloading and building modules with malicious
version strings could allow an attacker to write to arbitrary files on the
system the user has access to. This can only be triggered by explicitly
providing the malicious version strings to the toolchain, and does not affect
usage of @latest or bare module paths.
The toolchain now uses safer VCS options to prevent misinterpretation of
untrusted inputs. In addition, the toolchain now disallows module version
strings prefixed with a "-" or "/" character.
Thanks to splitline (@splitline) from DEVCORE Research Team for reporting this
issue.
This is CVE-2025-68119 and Go issue https://go.dev/issue/77099 .crypto/tls: handshake messages may be processed at the incorrect encryption level
During the TLS 1.3 handshake if multiple messages are sent in records that span
encryption level boundaries (for instance the Client Hello and Encrypted
Extensions messages), the subsequent messages may be processed before the
encryption level changes. This can cause some minor information disclosure if a
network-local attacker can inject messages during the handshake.
Thanks to Coia Prant (github.com/rbqvq) for reporting this issue.
This is CVE-2025-61730 and Go issue https://go.dev/issue/76443
View the release notes for more information:
https://go.dev/doc/devel/release#go1.25.6You can download binary and source distributions from the Go website:
https://go.dev/dl/To compile from source using a Git clone, update to the release with
git checkout go1.25.6
and build as usual.Thanks to everyone who contributed to the releases.
Cheers,
Original source Report a problem
The Go team - Jan 15, 2026
- Parsed from source:Jan 15, 2026
- Detected by Releasebot:Jan 16, 2026
January 15, 2026
Firestore Enterprise Native mode now includes Pipeline operations with Core CRUD and real time features, enabling advanced data retrieval. Android SDKs updated for Firebase AI Logic, Cloud Firestore, Crashlytics, plus PNV release and BoM v34.8.0. Learn more in release notes.
Cloud Firestore
Firestore Pipeline operations are now available as part of the Native mode of Firestore Enterprise edition. This mode integrates two distinct operations: Core and Pipelines. The Firestore Core operations provide the standard document Create, Read, Update, and Delete (CRUD) functionality, along with built-in support for real-time listen queries and offline persistence. The Firestore Pipeline operations employ a flexible query syntax enabling advanced data retrieval operations for applications. To learn more about Pipeline operations, see
Pipelines overview
.
SDK Releases
The Firebase Android SDKs for Firebase AI Logic, Cloud Firestore, Crashlytics, Crashlytics NDK, and Data Connect have been updated. The initial release of Firebase PNV is also available. For more details, check out the latest Android Release Notes. To get started with Firebase in Android, see Add Firebase to your Android Project.
The Firebase Android BoM (Bill of Materials) has been updated to v34.8.0. Learn how to add SDKs to your app using the Firebase BoM.
Original source Report a problem - Jan 15, 2026
- Parsed from source:Jan 15, 2026
- Detected by Releasebot:Jan 17, 2026
January 15, 2026
New releases empower reports with cross data source filtering, letting controls filter charts across sources, plus the ability to hide individual charts for all or specific viewers. Also introduced histogram charts for deeper data insights.
Feature
Cross data source filtering
This feature lets you override default field IDs so that controls on a report can filter charts that are based on different data sources.
Learn more about using controls across data sources.Feature
Show and hide individual charts and components
You can hide individual charts and components for all viewers or for a subset of viewers.
See Hide report components for viewers for more information.Feature
Histogram chart
You can visualize your data using histogram charts. Histograms are useful for understanding the shape, center, and spread of your data, which in turn can lead to insights that might be hidden in other types of charts, such as pie charts and bar charts.
Original source Report a problem
See the Histogram reference for more information. - Jan 14, 2026
- Parsed from source:Jan 14, 2026
- Detected by Releasebot:Jan 21, 2026
January 14, 2026
Firebase CLI (v15.3.0)
The latest Firebase CLI (v15.3.0) is now available. This version fixes pricing calculation for Cloud Functions with minInstances in newer regions and removes timeout when connecting to Cloud SQL. It also updates the Data Connect Emulator to v3.0.2 and includes several improvements and fixes for MCP tools and prompts. To use the Firebase CLI in your development environment, set up or update the CLI.
Original source Report a problem - Jan 14, 2026
- Parsed from source:Jan 14, 2026
- Detected by Releasebot:Oct 9, 2025
- Modified by Releasebot:Jan 17, 2026
January 14, 2026
SDK Releases
The Firebase JavaScript SDK (v12.8.0) is now available. For more details, see the Firebase JavaScript SDK release notes. To install the SDK, see Add Firebase to your JavaScript Project.
Original source Report a problem - Jan 14, 2026
- Parsed from source:Jan 14, 2026
- Detected by Releasebot:Jan 18, 2026
Editing password-protected Microsoft Office files directly in Google Drive
Google Workspace now lets you edit password‑protected Microsoft Office files directly in Docs, Sheets, and Slides. Open with Preview or Edit in Drive; Edit removes the password and enables in‑app editing, boosting interoperability with Microsoft.
We're excited to announce a major improvement to Microsoft Office interoperability in Google Workspace: you can now edit Microsoft Office files that are password-protected, directly within Docs, Sheets, and Slides.
When a user attempts to open a protected file in Drive, they will be prompted to enter the password with the option to View or Edit. Selecting “Preview” opens the document in read-only Preview mode without removing the password. New with this launch is the option to Edit, which will open the file for editing in Docs/Sheets/Slides and remove the password from the file.
This enables better interoperability between Workspace and Microsoft, allowing users for the first time to edit password protected files directly in Drive. Prior to this, users would have to download and rely on third party applications to remove passwords or edit password protected Microsoft files.
Getting started
- Admins: There is no admin control for this feature.
- End users: Visit the Help Center for more info on using this feature.
Rollout pace
- Rapid Release domains: Full rollout (1–4 days for feature visibility) starting on January 13, 2026, and ending on January 16, 2026
- Scheduled Release domains: Full rollout (1-3 days for feature visibility) starting on January 19, 2026, and ending January 21, 2026
Availability
- Available to all Google Workspace customers, Workspace Individual subscribers, and users with personal Google accounts
Resources
- Google Docs Editors Help: Edit an Office file directly in Docs, Sheets, or Slides