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

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

@@ -25,12 +25,12 @@
 type SortedConfig = string | { key: string; value: SortedConfig }[];
 
 // TODO(inlined): move to a file that's not about uploading source code
 export async function getFunctionsConfig(projectId: string): Promise<Record<string, unknown>> {
   try {
     return await functionsConfig.materializeAll(projectId);
   } catch (err: any) {
     logger.debug(err);
     let errorCode = err?.context?.response?.statusCode;
     if (!errorCode) {
       logger.debug("Got unexpected error from Runtime Config; it has no status code:", err);
       errorCode = 500;
@@ -47,7 +47,7 @@
   return {};
 }
 
 async function pipeAsync(from: archiver.Archiver, to: fs.WriteStream) {
   from.pipe(to);
   await from.finalize();
   return new Promise((resolve, reject) => {
@@ -59,7 +59,7 @@
 async function packageSource(
   sourceDir: string,
   config: projectConfig.ValidatedSingle,
   runtimeConfig: any,
 ): Promise<PackagedSourceInfo | undefined> {
   const tmpFile = tmp.fileSync({ prefix: "firebase-functions-", postfix: ".zip" }).name;
   const fileStream = fs.createWriteStream(tmpFile, {
@@ -101,15 +101,18 @@
         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) {
     throw new FirebaseError(
       "Could not read source directory. Remove links and shortcuts and try again.",
       {
         original: err,
         exit: 1,
       },
     );

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.