fix(cli): keep docker login output out of build logs

The registry login step's output was collected into the shared build log
buffer, so build logs on self-hosted and local builds always carried
docker's unencrypted-credentials warning — most confusingly right next to
the real error on failed builds. Route login output to debug logging only,
push a single 'Logged in to <registry>' marker into the build log on
success, and keep returning the full login output when the login itself
fails.

Author: myftija

.changeset/dry-mirrors-shake.md

@@ -0,0 +1,5 @@
+---
+"trigger.dev": patch
+---
+
+Build logs no longer include docker's registry login output, most notably the credential-storage warning on failed builds.

packages/cli-v3/src/deploy/buildImage.ts

@@ -514,19 +514,25 @@ async function localBuildImage(options: SelfHostedBuildImageOptions): Promise<Bu
     loginProcess.process?.stdin?.write(credentials.password);
     loginProcess.process?.stdin?.end();
 
+    // Login output (incl. docker's credential-storage warning) stays out of the build
+    // logs; it is fully visible at debug level and returned when the login itself fails.
+    const loginLogs: string[] = [];
+
     for await (const line of loginProcess) {
-      errors.push(line);
+      loginLogs.push(line);
       logger.debug(line);
     }
 
     if (loginProcess.exitCode !== 0) {
       return {
         ok: false as const,
         error: `Failed to login to registry: ${cloudRegistryHost}`,
-        logs: extractLogs(errors),
+        logs: extractLogs(loginLogs),
       };
     }
 
+    // `errors` is the shared build log buffer; keep a marker there so failure logs show auth ran
+    errors.push(`Logged in to ${cloudRegistryHost}`);
     options.onLog?.(`Successfully logged in to the remote registry`);
   }