Google Cloud Adds Date-Based Compute API Versions
Google Cloud has made multi-versioning of its Compute Engine API generally available, letting callers pin to dated, locked snapshots.
Updated on Nov. 14, 2026 in Data Centers

Google Cloud made multi-versioning of the Compute Engine API generally available, adding immutable date-stamped stable versions alongside the long-lived /v1 surface. Callers select a version with the X-Goog-Api-Version header or the $apiVersion query parameter.
Why it matters
The /v1 surface was a single, mutable production surface shared by every customer worldwide, so behavioral improvements risked breaking existing scripts or required multi-year migrations. Dated versions let customers adopt changes on their own schedule.
Stable versions are named YYYY-MM-DD and each is a locked snapshot of generally available features and defaults, with no breaking changes after publication. Preview versions carry a -preview suffix and a one-year lifespan, and the source does not say how long stable versions will be maintained.
The players
Google Cloud
Google Cloud is the cloud computing division of Alphabet Inc. that offers infrastructure, platform and software services to businesses worldwide.
The details
Each client library release for Python, Go, Java, Node.js, C#, Ruby and PHP now binds to one date-based version, and the Terraform google provider targets stable versions while google-beta targets preview versions. Date-based versions also turn on returnPartialSuccess for AggregatedList by default and return structured google.rpc.ErrorInfo errors.
Timeline
- 2026-09-01
First stable date-based Compute Engine API version released.
- 2026-10-01
Preview version 2026-10-01-preview available in all regions.
- 2026-11-14
Multi-versioning of the Compute Engine API made generally available.
Roadmap
Google's dated versioning follows a pattern Azure Resource Manager has used since its REST API launched, requiring a date-stamped api-version query parameter. Stripe's Stripe-Version header, with values such as 2026-10-28.endive, shows the same approach has spread across major cloud and payments platforms.
Developers who script against /v1 will keep working unchanged, since a request that names no version still receives /v1. Teams that want stable behavior can pin a dated version through the X-Goog-Api-Version header or the $apiVersion parameter.
The takeaway
Pinning a dated Compute Engine API version lets teams upgrade on their own schedule instead of absorbing silent changes to the shared production surface. Check which version your client libraries and Terraform provider target before the next release cycle.
Further reading
For background on the infrastructure behind these services, see Data Centers.
Source note: This article includes information reported by InfoQ.



