GCP Function Runtime Version

Sign in to the Google Cloud Management Console.

Select the GCP project that you want to examine from the console top navigation bar.

Locate the function based on its generation:

• 1st gen: Cloud Functions console

• 2nd gen: Cloud Run console

Click on the name (link) of the function/service that you want to examine, then open the SOURCE tab to access the language runtime details.

Check the Runtime attribute value to determine the language runtime version configured for the selected function. Compare it with the latest runtime available for that generation. A 1st-gen function cannot use 2nd-gen-only runtimes, so it should use the newest runtime available for 1st gen. If the Runtime attribute is not configured to use the latest language runtime version available for its generation, the selected function is using an outdated and/or decommissioned runtime.

Repeat steps no. 3 – 5 for each Google Cloud function created for the selected GCP project.

Repeat steps no. 2 – 6 for each project deployed within your Google Cloud account.

Run projects list command (Windows/macOS/Linux) with custom query filters to list the ID of each project available in your Google Cloud Platform (GCP) account:

gcloud projects list
  --format="table(projectId)"

The command output should return the requested GCP project ID(s):

PROJECT_ID
cc-bigdata-project-123123
cc-iot-app-project-112233

Run functions list command (Windows/macOS/Linux) using the ID of the GCP project that you want to examine as the identifier parameter and custom query filters to describe the name and the region of each Google Cloud function deployed within the selected project:

gcloud functions list
  --project cc-bigdata-project-123123
  --format="(NAME,REGION)"

The command output should return the requested function names and their regions:

NAME                  REGION
cc-web-app-function   us-central1
cc-stream-function    us-central1

Run functions describe command (Windows/macOS/Linux) using the name of the Google Cloud function that you want to examine as the identifier parameter, to describe the generation (environment) and the language runtime ID configured for the selected function. GCP only sets the environment field for 2nd-gen functions and reports the runtime under a different field depending on generation, so default the generation to GEN_1 and request both possible runtime fields:

gcloud functions describe cc-web-app-function
  --region=us-central1
  --format="value(environment.yesno(no='GEN_1'), runtime, buildConfig.runtime)"

The command output should return the function generation (GEN_1 or GEN_2) and the requested runtime ID, in that order:

GEN_1   python311

Compare the runtime ID returned by the functions describe command output with the latest runtime available for that generation. A 1st-gen function cannot use 2nd-gen-only runtimes, so it should use the newest runtime available for 1st gen. If the runtime ID is not the latest language runtime version available for the function's generation, the selected function is using an outdated and/or decommissioned runtime.

Repeat steps no. 5 and 6 for each Google Cloud function created for the selected GCP project.

Repeat steps no. 3 – 7 for each GCP project deployed in your Google Cloud account.

Sign in to the Google Cloud Management Console.

Select the GCP project that you want to access from the console top navigation bar.

Locate the function based on its generation:

• 1st gen: Cloud Functions console

• 2nd gen: Cloud Run console

Click on the name (link) of the function/service that you want to configure, listed in the Name column.

Open the SOURCE tab to access the language runtime details for the selected function.

Choose EDIT and select the latest runtime available for the function's generation from the Runtime dropdown list. If a 1st-gen function is already using the newest runtime available for 1st gen, migrate it to 2nd gen to access newer runtimes (for example Go, Ruby 4.0, and newer Node.js, Python, and Java versions).

Choose SAVE AND REDEPLOY to save the changes and redeploy your function.

Repeat steps no. 4 – 7 for each Google Cloud function that you want to configure, available for the selected GCP project.

Repeat steps no. 2 – 8 for each project deployed within your Google Cloud account.

Run functions runtimes list command (Windows/macOS/Linux) to list the language runtimes supported by Google Cloud Functions. The ENVIRONMENTS column shows which generation (1st gen and/or 2nd gen) supports each runtime:

gcloud functions runtimes list
  --region=us-central1
  --format="table(name,environments)"

The command output should return the list of supported language runtimes:

NAME        ENVIRONMENTS
nodejs22    ['GEN_1', 'GEN_2']
nodejs24    ['GEN_2']
python312   ['GEN_1', 'GEN_2']
python314   ['GEN_2']
java17      ['GEN_1', 'GEN_2']
java25      ['GEN_2']
php82       ['GEN_1', 'GEN_2']
php85       ['GEN_2']
go126       ['GEN_2']
ruby40      ['GEN_2']
dotnet10    ['GEN_2']

Run functions deploy command (Windows/macOS/Linux) using the name of the Google Cloud function that you want to configure as the identifier parameter, to upgrade to the latest runtime available for the function's generation. Use the --runtime parameter to specify a runtime valid for that generation. To adopt a 2nd-gen-only runtime, redeploy the function as 2nd gen using the --gen2 flag (e.g. --runtime=python314):

gcloud functions deploy cc-web-app-function
  --region=us-central1
  --entry-point hello_http
  --trigger-http
  --runtime=python312
  --format="value(environment.yesno(no='GEN_1'), runtime, buildConfig.runtime)"

The command output should return the function generation (GEN_1 or GEN_2) and the new runtime ID, in that order:

GEN_1   python312

Repeat steps no. 1 – 4 for each Google Cloud function that you want to configure, created for the selected GCP project.

Repeat steps no. 1 – 5 for each project deployed within your Google Cloud account.