Available in Classic and VPC
Cloud Functions provides isolated runtimes and supports multiple languages and versions. You can implement a code by selecting a runtime that matches your environment. Runtime versions of operating systems/languages may change or be deprecated depending on the service End Of Life (EOL), security vulnerabilities, and internal management policies.
Supported runtime
Cloud Functions supports the following language runtimes. Runtime ID values are required when creating/editing actions through APIs.
| Runtime | Runtime ID | Deprecation (planned) |
|---|---|---|
| Node.js 22 | nodejs:22 | |
| Python 3.13 | python:3.13 | |
| Java 8 | java | |
| Java 21 | java:21 | |
| Swift 3.1.1 | swift:3.1.1 | |
| PHP 7.3 | php:7.3 | |
| Go 1.19 | go:1.19 | |
| .Net Core 2.2 | dotnet:2.2 | |
| Custom Image | custom image |
Runtime update policy
Cloud Functions regularly checks and updates security vulnerabilities in each runtime environment and included languages for you to focus only on business logic. Cloud Functions runtime sub-versions may change for security vulnerabilities or feature improvements when OS/language vendor updates are available. Runtimes may be deprecated depending on vendor security update availability. For more information about runtime deprecation, see Runtime deprecation.
Runtime updates are announced in advance through email or SMS considering service impact. You need to check for any impacts. Library compatibility issues in actions are not technically supported. For more information, see Runtime usage recommendations.
Runtime deprecation
Cloud Functions runtimes may be deprecated due to factors such as OS and programming language vendor policies or internal service maintenance. Additionally, a runtime may be deprecated if security updates for its components can no longer be provided. No security updates or technical support are provided for deprecated runtimes.
Support for Cloud Functions is provided according to the following criteria:
- At least 90 days before deprecation: Notification of runtime deprecation
- On the date of deprecation: You cannot create a new action. Existing actions can be edited and run.
- 30 days after deprecation: You cannot create/edit actions.
- Existing actions can still run.
The runtime deprecation policy is necessary for efficient Cloud Functions use. We recommend migration within the usage period for stable and secure Cloud Functions use.
New Regions exclude runtimes planned for deprecation.
Deprecated runtimes
Information about deprecated runtimes is as follows:
| Runtime | Runtime ID | Deprecation date |
|---|---|---|
| Node.js 6 | nodejs:6 | September 18, 2025 |
| Node.js 8 | nodejs:8 | September 18, 2025 |
| Node.js 12 | nodejs:12 | September 18, 2025 |
| Node.js 16 | nodejs:16 | September 18, 2025 |
| Python 3.6 | python:3.6 | September 18, 2025 |
| Python 3.7 | python:3.7 | September 18, 2025 |
| Python 3.11 | python:3.11 | September 18, 2025 |
| PHP 7.1 | php:7.1 | September 18, 2025 |
| Go 1.11 | go:1.11 | September 18, 2025 |
- Deprecation date is based on Korean Standard Time (KST).
- Supported languages and versions are disclosed in advance. However, they may be deprecated without prior notice due to vendor issues or internal decisions.
Runtime usage recommendations
Libraries included in each runtime may be deprecated or versioned up for maintenance purposes. It is recommended to package essential libraries with your code, considering its compatibility and impact. Note that the supported operating systems and versions for each runtime are subject to change based on internal policies. Therefore, it is recommended to write platform-independent code. For these issues, updates or technical support are not provided.