fix: only show runtime config deprecation warning for user-defined config (#8963)

* fix: only show runtime config deprecation warning for user-defined config

The runtime config deprecation warning was appearing for all v1 function
deployments, even when users weren't using functions.config(). This was
because the default Firebase config values (projectId, storageBucket) are
always included in the runtime config.

This fix checks if the runtime config contains any keys beyond the default
'firebase' key before showing the deprecation warning. Users who only have
the default Firebase config will no longer see false positive warnings.

Fixes #8925

* docs: add CHANGELOG entry for runtime config warning fix

* chore: update runtime config deprecation date to March 2026

* refactor: simplify runtime config user check logic

Use Object.keys().some() directly for cleaner, more readable code

Author: taeold

CHANGELOG.md

@@ -1,3 +1,4 @@
+- Updated untime config deprecation warning to no longer shows for v1 functions that only use default Firebase config. (#8963)
 - Updated Data Connect emulator to v2.11.1, which:
   - [added] Add an app watch that collects embedded GQL into the connector folder.
   - [fixed] Handle foreign key constraint error as FailedPrecondition.

src/deploy/functions/prepareFunctionsUpload.ts

@@ -101,8 +101,11 @@ async function packageSource(
         mode: 420 /* 0o644 */,
       });
 
-      // Log deprecation warning when runtime config is being packaged
-      logFunctionsConfigDeprecationWarning();
+      // Only warn about deprecated runtime config if there are user-defined values
+      // (i.e., keys other than the default 'firebase' key)
+      if (Object.keys(runtimeConfig).some((k) => k !== "firebase")) {
+        logFunctionsConfigDeprecationWarning();
+      }
     }
     await pipeAsync(archive, fileStream);
   } catch (err: any) {

src/functions/deprecationWarnings.ts

@@ -1,14 +1,14 @@
 import { logWarningToStderr } from "../utils";
 
-const FUNCTIONS_CONFIG_DEPRECATION_MESSAGE = `DEPRECATION NOTICE: Action required to deploy after Dec 31, 2025
+const FUNCTIONS_CONFIG_DEPRECATION_MESSAGE = `DEPRECATION NOTICE: Action required to deploy after March 2026
   
   functions.config() API is deprecated.
-  Cloud Runtime Configuration API, the Google Cloud service used to store function configuration data, will be shut down on December 31, 2025. As a result, you must migrate away from using functions.config() to continue deploying your functions after December 31, 2025.
+  Cloud Runtime Configuration API, the Google Cloud service used to store function configuration data, will be shut down in March 2026. As a result, you must migrate away from using functions.config() to continue deploying your functions after March 2026.
   
   What this means for you:
   
-  - The Firebase CLI commands for managing this configuration (functions:config:set, get, unset, clone, and export) are deprecated. These commands no longer work after December 31, 2025.
-  - firebase deploy command will fail for functions that use the legacy functions.config() API after December 31, 2025.
+  - The Firebase CLI commands for managing this configuration (functions:config:set, get, unset, clone, and export) are deprecated. These commands will no longer work after March 2026.
+  - firebase deploy command will fail for functions that use the legacy functions.config() API after March 2026.
   
   Existing deployments will continue to work with their current configuration.