← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

Google Cloud Compute Engine API Adopts Immutable Date-Based Versioning

🔄 Updated 7d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Compute Engine API now offers immutable, date-stamped versions.
  • Stable versions are quarterly, starting 2026-09-01, with preview versions available.
  • New versions enable safer IAM permissions and updated error formats.
  • Client libraries and gcloud tooling will integrate with the new versions.

New API Versioning System

Google Cloud has introduced multi-versioning for its Compute Engine API, making it generally available. This update adds immutable, date-stamped API versions, such as YYYY-MM-DD, which will be released quarterly. The first stable version is 2026-09-01. Preview versions, identified by a '-preview' suffix, will have a one-year lifespan. The existing /v1 API will remain available indefinitely.

Addressing /v1 Limitations

The previous /v1 API was a single, mutable production surface, meaning any changes, even minor improvements, could break existing customer scripts or require extensive migrations. The new interface-based versioning, aligned with Google's AIP-185, creates locked snapshots of features and defaults for each stable version, preventing breaking changes after publication.

Key Differences for Callers

Callers will observe three main differences. Firstly, new versions default to returning partial results from AggregatedList, unlike /v1 which requires explicit configuration. Secondly, error bodies now use a structured google.rpc.ErrorInfo format with reason, domain, and metadata. Thirdly, new versions allow for tighter IAM permission checks and safer configuration defaults, moving away from older resource schemas.

Tooling Integration

Most users will interact with these changes through updated tooling. Client libraries for Python, Go, Java, Node.js, C#, Ruby, and PHP will bind to specific date-based versions while maintaining existing import paths. The `gcloud compute` command will target the bundled stable version, and `gcloud preview compute` will target preview versions, with existing `compute`, `beta`, and `alpha` scripts remaining unchanged. The Terraform google provider will also target stable versions.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Google Cloud has made multi-versioning for the Compute Engine API generally available, introducing immutable, date-stamped API versions alongside the existing /v1 surface. This change addresses issues with the mutable /v1 API, which previously risked breaking existing scripts with any behavioral improvements. The new system provides stable, locked snapshots of features and defaults, allowing for safer configuration and modernizing error formats without impacting older integrations.