This guide explains the standard release and update processes for Looker (Google Cloud core), along with best practices and variations that may better fit your needs.
Development and release cycle
A new minor version of Looker (Google Cloud core) is deployed over the course of roughly a couple of weeks. No new releases nor deployments happen in the month of December.
At times, small update patches will be released for fixes that shouldn't wait for the next release. These are nearly always fixes for critical product or security issues. Ideally, no new features would ever be included in a patch release. The application of patch updates follows the same process as upgrading during a standard release.
Release numbers
The release numbering scheme for Looker (Google Cloud core) uses the same release numbering as for Looker (original) instances, which is a three-number sequence: X.Y.Z, where X is the last two digits of the year of the release, Y is the monthly version (starting with 0 in January, and using even numbers for each subsequent month), and Z is the patch release version. For example, Looker (Google Cloud core) 26.10.1 would be the first patch of the Looker (Google Cloud core) release from June of 2026.
Release notes
Stay current with any new features and issue fixes by checking out the release notes. See the Looker releases page for links to the release notes and changelog for the latest release.
Release channels
Release channels offer greater control and predictability over when new features and updates are applied to your Looker (Google Cloud core) instances. By choosing a release channel, you can balance your organization's needs for early access to the latest capabilities against the need for operational stability in production environments.
During the preview launch, Rapid and Regular release channels are available. There is also a No channel option. The following sections describe each one.
Rapid release channel
The Rapid release channel provides the earliest access to new features and improvements. The Rapid channel is ideal for non-production, staging, or testing instances, allowing you to validate internal workflows and test new capabilities. When a Looker (Google Cloud core) instance uses the Rapid release channel, maintenance windows and deny maintenance periods can't be set for that instance.
If a Looker instance doesn't have a release channel selected, and you enroll that instance in the Rapid channel, there is no change to the release cadence for that instance. The Rapid channel receives new Looker versions once a month and receives security updates as soon as they're available.
If you opt in to maintenance notifications, you'll receive an email notification of upcoming instance upgrades for every patch version rollout. The email will be sent to the email address that's associated with your Google Account at least 72 hours before an upgrade is scheduled.
Regular release channel
The Regular release channel offers balanced stability, with updates applied on a monthly basis. The Regular channel is the recommended channel for production instances, providing a predictable update cadence while still delivering new features and issue fixes in a timely manner. The Regular channel receives Looker versions one month after the Rapid channel receives Looker versions.