What changed
Time to bail on Cloud Run functions on PHP 8.2? Act. You can stay. After June 30, 2027, PHP 8.2 functions cannot be created or updated, and may be disabled.
On our scale this is Act: change a setting or plan before the date. You can stay.
Google decommissions the PHP 8.2 runtime (php82) for Cloud Run functions on June 30, 2027. After that you cannot create or update these functions, and they may be disabled.
Here are the facts we checked:
- Decommission date: June 30, 2027 (Google Cloud)
- Runtime: PHP 8.2, runtime ID php82 (1st gen and Cloud Run functions) (Google Cloud)
- Deprecated since: December 31, 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 php82 runtime on Cloud Run has the same dates (Google Cloud)
- Can the dates change?: Google says key dates might be delayed (Google Cloud)
- Newer runtimes: php83 is decommissioned June 30, 2028, php84 June 30, 2029, php85 June 30, 2030 (Google Cloud)
- Functions still on PHP 8.2: Cannot be updated after June 30, 2027 and may be disabled (Google Cloud)
You can stay on Cloud Run functions. You have to change a setting or plan before the date.
Leaving is a choice here, not a must.
Google Cloud is the main source for this page. Cloud Run functions has not said more than what is listed here. If a fact is not on this page, we do not know it yet.
Who is affected
Functions still on PHP 8.2: Cannot be updated after June 30, 2027 and may be disabled.
The date to remember is June 30, 2027. Make the change before then.
What to do before June 30
- Find functions on PHP 8.2. In the console, check the runtime of each function. Note every one on php82.
- Change the runtime. Set the runtime to php84 or php85 and update your dependencies.
- Deploy each function again. Deploy and test every function before June 30, 2027.
A few tips:
- Make the change yourself before the date. Do not wait for the last reminder email.
- Write down your current plan or settings first, so you can compare after the change.
- After the change, open your settings again and check that it worked.
How to tell your users
If the change affects your members or team, send one short email. Say what changes for them and when. 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.
Options people mention
Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.
Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.
Questions people ask
No questions collected yet.
Sources