Google renames its API desert 'versions', makes you ask for water politely.

Google Cloud has introduced date-based versions for its Compute Engine API, adding immutable quarterly releases named like 2026-09-01 alongside the existing, mutable /v1 endpoint. The change, driven by engineer Michael Murstein, addresses the problem of a single global API surface where any improvement risked breaking customer scripts. Callers can specify a version via a header or query parameter; if they don't, they'll keep using the original /v1, which has no end-of-life.

For engineers, this means future tooling and client libraries will default to these new, frozen snapshots, changing some defaults and error formats. The move lets Google tighten legacy permissions and modernize schemas without breaking old automation. The takeaway? It's another layer of abstract complexity in cloud APIs, where even a simple list query now requires you to remember which calendar date holds your preferred behavior.