Google Cloud runtime support materials and industry write-ups place Node.js 20 managed-runtime decommission on 30 October 2026. Source-based Functions/Run are in scope; custom containers usually are not — but still need your patches. The steps below are read-only first.
- List every GCP project that might host Node services. Include shared VPC host projects and old “experiments” folders that still serve production traffic.
- Answer the matrix. Select products, deploy shape, and timing. Copy the command starters and checklist into your ops doc.
- Classify source vs container. For each Cloud Run service, note whether it deploys from source/buildpacks or from an image digest you build.
- List Cloud Functions runtimes. Use
gcloud functions listwith a table format that includesbuildConfig.runtime/ runtime fields; filter rows equal tonodejs20. - Describe Cloud Run services. For managed-runtime suspects,
describeeach service/job and record runtime or base image metadata you rely on. - Prioritize production source deploys. Schedule runtime bumps (to a currently supported Node runtime per live docs) in CI/Terraform before create/update blocks.
- Self-check with a canary redeploy. Redeploy one non-critical function/service on the new runtime; run smoke tests including native addons.
- Re-read live runtime support pages on migration week. Successor runtime IDs and exact enforcement language can change; treat this static page as a helper, not the source of truth.
This tool never calls Google APIs and never stores project IDs you type elsewhere — keep credentials in your own shell.