timetobail
My stack

Playbook for makers · Forced move · free while in beta

Act

Go 1.25 functions on Google Cloud: decommissioned April 1, 2027

Readers can stay on Cloud Run functions: they change a setting or plan. Help the ones who would rather leave.

165 days left · April 1, 2027 · Public page

Low switching pressure28/100

An estimate from the deadline, cost, discussion and need to move. It is not a product rating.

What goes into it

Confidence: medium.

deadline8/30
money14/25
attention0/25
audience0/12
force6/8
  • Hard deadline in 165 days.
  • The change is forced: it reaches users even if they wait.

  1. 1 Related discussions

    Only threads tied to this event that talk about leaving, moving or prices. Saved, not live. Check the date and read the thread before replying.

    No live threads yet.

  2. 2 What people ask

    No common questions yet.

  3. 3 Reply templates

    Answer the question first. Link only if it helps. Always keep the disclosure line. Never post the same text twice.

    Helpful first
    Sorry you have to deal with this. You can stay on Cloud Run functions. Here is what to change before April 1, 2027:

1. Find functions on Go 1.25. In the console, check the runtime of each function. Note every one on go125.
2. Change the runtime. Set the runtime to go126 or go127 and update your dependencies.
3. Deploy each function again. Deploy and test every function before April 1, 2027.

If they would rather leave, describe a verified way <your product> can help: <your link>
[Disclosure: I build <your product>.]
    Short answer
    You have until April 1, 2027. You can stay on Cloud Run functions. First: find functions on Go 1.25. Then change the runtime.
Happy to help if you get stuck.
[Disclosure: I build <your product>.]
    If you do nothing
    > What happens if I do nothing?

Google Cloud says:
- If you do nothing: Functions that stay on a decommissioned runtime may be disabled.

You can stay on Cloud Run functions. To choose when it happens, make the change yourself before April 1, 2027.
Details: https://docs.cloud.google.com/functions/docs/runtime-support

I build a tool for people who would rather leave: <your link>
[Disclosure: I build <your product>.]

  4. 4 Switch-page builder

    Create a draft “Switch from Cloud Run functions” page. Add your product, review every claim, then copy HTML or Markdown. Your product claims need your own evidence.

    • Add your product name to replace “Your product”.
    Preview

    Switch from Cloud Run functions to Your product

    Cloud Run functions on Go 1.25: a change is due by April 1. You can stay on Cloud Run functions. If you would rather leave, here is how to move to Your product.

    What changes at Cloud Run functions

    Google decommissions the Go 1.25 runtime (go125) for Cloud Run functions on April 1, 2027. After that you cannot create or update these functions, and they may be disabled.

    • Decommission date: April 1, 2027 (Google Cloud)
    • Runtime: Go 1.25, runtime ID go125 (Cloud Run functions) (Google Cloud)
    • Deprecated since: October 1, 2026 (Google Cloud)
    • After decommission: You can no longer create new workloads or update existing ones on the runtime (Google Cloud)
    • If you do nothing: Functions that stay on a decommissioned runtime may be disabled (Google Cloud)
    • Cloud Run source deploys: The go125 runtime on Cloud Run has the same dates (Google Cloud)
    • Can the dates change?: Google says key dates might be delayed (Google Cloud)
    • Older Go runtime: Go 1.24: decommissioned earlier, on March 2, 2027 (Google Cloud)
    • Go version policy: Each Go release is supported until there are two newer major releases, so dates can move (Google Cloud)
    • Newer runtimes: Go 1.26 (go126) dates are approximate (deprecated Feb/March 2027); Go 1.27 (go127) deprecated Aug/Sept 2027 (Google Cloud)
    • Functions still on Go 1.25: Cannot be updated after April 1, 2027 and may be disabled (Google Cloud)

    You can stay on Cloud Run functions if you make the change. This page is for people who would rather leave.

    What Your product gives you

    Write two or three short lines here. Say what Your product does, who it is for, and what it costs. Use only facts you can show.

    How to move from Cloud Run functions to Your product

    1. Save what you need from Cloud Run functions. Keep a copy before you cancel anything.
    2. Import into Your product. Say which files you accept and how long an import takes.

    Tell readers the key date: April 1, 2027.

    Questions people ask

    If Your product has a direct answer to one of these, add it here. Keep it short and true.

    How to help new users settle in

    Send one short email. Say what changed, where to find you now, and what they need to do. Put the most important line first.

    If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

    Sources

  5. 5 Search ideas to validate

    suggested, not measured Phrases people may search when a tool changes like this. We have no search volume data for them.

    • cloud run functions on go 1.25
    • cloud run functions alternative
    • cloud run functions alternatives
    • cloud run functions export
    • how to leave cloud run functions
    • switch from cloud run functions
    • cloud run functions migration
    • cloud run functions migration 2027