ST-2026-170 · Runtimes & developer platforms
Google Cloud schedules Buildpacks Go 1.23 decommission for 21 August
Google Cloud's Buildpacks runtime lifecycle schedule lists Go 1.23 (`go123`) for decommission on 21 August 2026, after a deprecation period that began on 21 February 2026.
Previous state
During the documented deprecation period, teams can generally continue creating new workloads and updating existing workloads that use the Go 1.23 Buildpacks runtime.
Current state
From the scheduled decommission date, new workloads cannot be created and existing workloads cannot be updated using `go123`; workloads that continue to use a decommissioned runtime may be disabled.
Affected users
Who needs to care
Teams deploying source-built Google Cloud workloads that still depend on the Buildpacks Go 1.23 runtime ID `go123`.
Required response
What to do
Inventory `go123` workloads and migrate them to a supported newer Go runtime before the current decommission boundary, while rechecking Google's live schedule for any postponement.
Evidence boundary
What the source does not prove
Google lists 21 August 2026 as the current decommission date but states that availability and key dates may be delayed and specifically notes that Go lifecycle dates can be postponed depending on newer Go releases. The record therefore preserves 21 August as a scheduled, not immutable, boundary.
Lifecycle history
Dated event sequence
- Go 1.23 deprecation period begins
Google's Buildpacks lifecycle schedule lists 21 February 2026 as the Go 1.23 deprecation date.
- Current scheduled decommission
Google's current schedule lists Go 1.23 for decommission, subject to Google's stated schedule-delay and Go-release-policy caveats.
Evidence ledger
First-party sources
- 01Google Cloud — Google Cloud's buildpacks runtime lifecycle
Official Buildpacks runtime lifecycle schedule; page last updated 29 July 2026 UTC · 2026-07-29
Open official source ↗