bug: Deploy doesn't push image to registry in CLI v4.3.0

[fab-uleuh]

Provide environment information

System:
OS: Linux 5.15 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
CPU: (4) x64 AMD EPYC 9354P 32-Core Processor
Memory: 9.60 GB / 15.61 GB
Container: Yes
Shell: 5.1.16 - /bin/bash
Binaries:
Node: 20.13.1 - /root/.nvm/versions/node/v20.13.1/bin/node
npm: 10.9.4 - /root/omstudio/node_modules/.bin/npm
pnpm: 9.14.2 - /root/.local/share/pnpm/pnpm

Describe the bug

When deploying with CLI v4.3.0 to a self-hosted instance, the image is built but never pushed to the local registry. This causes tasks to fail with "no such image" error.

Steps to reproduce:

1. Self-hosted Trigger.dev v4 with Docker Compose and local registry
2. Run: pnpm dlx trigger.dev@4.3.0 deploy -a https://my-instance.com
3. Deploy succeeds: "Successfully deployed version 20251214.XX"
4. Image is NOT in registry (curl localhost:5000/v2/_catalog shows empty)
5. Trigger a task → fails with "Failed to pull image - no such image"

Expected behavior:
Image should be pushed to the registry configured in DEPLOY_REGISTRY_HOST

Actual behavior:
Image is never pushed to the registry

Workaround:
Use CLI version 4.0.1:
pnpm dlx trigger.dev@4.0.1 deploy -a https://my-instance.com --skip-update-check
This correctly pushes the image to the registry.

Environment:

• CLI: trigger.dev@4.3.0 (broken) vs @4.0.1 (works)
• Webapp: ghcr.io/triggerdotdev/trigger.dev:v4-beta
• Registry: localhost:5000 with htpasswd auth
• OS: Ubuntu 22.04

Regression:
This is a regression between v4.0.1 and v4.3.0

Reproduction repo

/

To reproduce

/

Additional information

No response