Skip to content
Source: InfoQ

☁️Google Cloud Makes Compute Engine API Versioning Generally Available With Quarterly Stable Releases

Your Terraform and gcloud pins just got a lot safer

TL;DR

Google Cloud made Compute Engine API multi-versioning generally available, with immutable date-stamped stable versions shipping quarterly from 2026-09-01. Pin one with a header and breaking changes stop surprising you. Most teams will see it through gcloud and Terraform, not raw headers.

Google just gave Compute Engine the versioning model everyone else already had. Multi-versioning is now generally available, and every stable version is named YYYY-MM-DD and ships quarterly, starting 2026-09-01. Each one is a locked snapshot of everything GA at that date, and nothing breaking gets changed after publication. Why you should care: if you run fleets, this changes how your queries fail. The date-based versions turn on partial results for AggregatedList by default, so one bad zone stops taking down a fleet-wide query. Your gcloud compute commands target the bundled stable version, and Terraform's google provider follows stable while google-beta follows preview. Check your pins before the first quarterly bump lands. The details: preview versions carry a -preview suffix and live for one year. The /v1 surface has no end-of-life date, so nothing is forced on you today. Google is also the last of the big three clouds to let you pin a version per request, which, yeah, is overdue. Pin with the X-Goog-Api-Version header or the $apiVersion query parameter.

Google Cloud Makes Compute Engine API Versioning Generally Available With Quarterly Stable Releases — InfoQ

Key Points

1

Stable versions are named YYYY-MM-DD and released quarterly, starting with 2026-09-01, each a locked snapshot of all generally available features and defaults at that date.

Keep reading — it's free

Enter your email to keep reading — plus the best of AI & tech, daily. Free, forever.

Also get
or

Already a member? Sign in

Google CloudCompute EngineAPI VersioningTerraformgcloud

Comments

Subscribe to join the conversation...

Be the first to comment