Title: bug: Cloud deploy fails at registry push with anonymous-token 401 on v4.4.5 and v4.4.6 · Issue #3732 · triggerdotdev/trigger.dev · GitHub
Open Graph Title: bug: Cloud deploy fails at registry push with anonymous-token 401 on v4.4.5 and v4.4.6 · Issue #3732 · triggerdotdev/trigger.dev
X Title: bug: Cloud deploy fails at registry push with anonymous-token 401 on v4.4.5 and v4.4.6 · Issue #3732 · triggerdotdev/trigger.dev
Description: Summary trigger.dev deploy to Trigger.dev Cloud fails at the final image-push step with a 401 from registry.depot.dev. The build itself succeeds end-to-end; only the push falls through to an "anonymous token" request which Depot rejects....
Open Graph Description: Summary trigger.dev deploy to Trigger.dev Cloud fails at the final image-push step with a 401 from registry.depot.dev. The build itself succeeds end-to-end; only the push falls through to an "anony...
X Description: Summary trigger.dev deploy to Trigger.dev Cloud fails at the final image-push step with a 401 from registry.depot.dev. The build itself succeeds end-to-end; only the push falls through to an "...
Opengraph URL: https://github.com/triggerdotdev/trigger.dev/issues/3732
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"bug: Cloud deploy fails at registry push with anonymous-token 401 on v4.4.5 and v4.4.6","articleBody":"## Summary\n\n`trigger.dev deploy` to Trigger.dev Cloud fails at the final image-push step with a 401 from `registry.depot.dev`. The build itself succeeds end-to-end; only the push falls through to an \"anonymous token\" request which Depot rejects.\n\nReproduced identically on CLI **v4.4.5** and **v4.4.6**, across multiple consecutive deploys. Local environment is clean (details below), so this looks server-side — the per-build Depot token minted by the webapp appears to lack registry-push scope, or is being stubbed.\n\n## Error\n\n```\n#28 ERROR: failed to push registry.depot.dev/0tz24lsnjm:TAG: failed to authorize: failed to fetch anonymous token: unexpected status: 401 Unauthorized\n------\n > exporting to image:\n------\nError: failed to solve: failed to push registry.depot.dev/0tz24lsnjm:TAG: failed to authorize: failed to fetch anonymous token: unexpected status: 401 Unauthorized\n```\n\n(Image tag redacted as `TAG`; original was an opaque hex string.)\n\n## Reproduction\n\n```\nnpx trigger.dev@4.4.6 deploy\n# also failed identically with:\nnpx trigger.dev@4.4.5 deploy --skip-update-check\n```\n\nBuild succeeds through `#27 [final 3/3] COPY --from=indexer ...`. Failure begins at `#28 exporting to image → pushing layers` for `registry.depot.dev/0tz24lsnjm:TAG`.\n\n## Environment\n\n- CLI: **v4.4.5 and v4.4.6**, both fail identically\n- `@trigger.dev/sdk`, `@trigger.dev/build`, `@trigger.dev/python`: 4.4.6\n- OS: Windows 11, Node (via `npx`)\n- Cloud target: `https://api.trigger.dev` (not self-hosted)\n\n## Locally cleared\n\n- `whoami` returns the correct account and project (URL `https://api.trigger.dev`)\n- Project ref in `trigger.config.ts` matches the dashboard\n- `trigger.config.ts` is vanilla — no `build.image`, no `selfHosted`, no custom registry\n- No local `depot` CLI installed\n- No `DEPOT_TOKEN`, no `~/.depot/config.json`\n- No `DEPOT_*` or `TRIGGER_*` env vars set in the shell\n\nThe CLI has no input path that controls the Depot push credential for Cloud builds — those are minted server-side per `remoteImageBuilder.server.ts → createRemoteImageBuild`.\n\n## Identifying info\n\n- Org: **BD Online Ventures LLC**\n- Project ref: `proj_ohzzrjqadpcnxvizsrig`\n- Internal project ID: `cmphw1f1z078yon0hrgmdvi0t`\n- Failing deployment: `deployment_qwkvcpchx2zu4b76x7u1f` (others in same session, all same symptom)\n- Depot org from error: `0tz24lsnjm`\n\n## Hypotheses (from reading the source)\n\nReading `packages/cli-v3/src/deploy/buildImage.ts` and `apps/webapp/app/v3/remoteImageBuilder.server.ts`:\n\n1. **Build token has build-scope but not registry-push scope.** Build machine launches successfully (`[depot] launching amd64 machine` works → token is valid), but push at `#28` falls through to anonymous → 401. This signature suggests scope, not validity.\n2. **`externalBuildData` stubbed to `{buildToken: \"-\", buildId: \"-\", projectId: \"-\"}`.** The webapp returns these sentinels when `initialStatus === \"PENDING\"`, `isNativeBuild`, or `isLocalBuild` is true in the deployment-create payload. Less likely given the machine launches, but worth confirming on the server side.\n3. **Token expiry between machine launch and push.** Less likely given the build completes in seconds.\n\n## Ask\n\nCould someone with backend access inspect the `createRemoteImageBuild` call for project `proj_ohzzrjqadpcnxvizsrig` and confirm whether the minted build token has registry-push scope on Depot org `0tz24lsnjm`?\n\nHappy to share full build logs / debug-level CLI output via DM if useful — omitted here since the build content is project-specific.\n","author":{"url":"https://github.com/brianmdevine","@type":"Person","name":"brianmdevine"},"datePublished":"2026-05-23T15:34:02Z","url":"https://github.com/triggerdotdev/trigger.dev/issues/3732"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react-reconciler,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@d5750093facf |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:b9c57c23-ad63-9a33-39c9-ba9353aa09cd |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 8BB4:F0723:3FFF8BB:5704968:6AFAEE77 |
| html-safe-nonce | 6bf453622442c27c621ebc69e3cba10dc692098b4554a0c65cb5d6b604eb72e4 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI4QkI0OkYwNzIzOjNGRkY4QkI6NTcwNDk2ODo2QUZBRUU3NyIsInZpc2l0b3JfaWQiOiI3MDgyODc1NjM5OTg4ODM0NDciLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | c6613fc443b282f801720c660d77108988bcb14c8ba19e95a3295466eda7f9c6 |
| hovercard-subject-tag | issue:4508724392 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/triggerdotdev/trigger.dev/3732/issue_layout |
| twitter:image | https://opengraph.githubassets.com/bd374db9a6113d8ac47dbd7020208a02e2643380a12125c53e394f9a3d99b633/triggerdotdev/trigger.dev/issues/3732 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/bd374db9a6113d8ac47dbd7020208a02e2643380a12125c53e394f9a3d99b633/triggerdotdev/trigger.dev/issues/3732 |
| og:image:alt | Summary trigger.dev deploy to Trigger.dev Cloud fails at the final image-push step with a 401 from registry.depot.dev. The build itself succeeds end-to-end; only the push falls through to an "anony... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | brianmdevine |
| hostname | github.com |
| expected-hostname | github.com |
| None | 0178036d8230524a18422872393ab7e708443ae4c2047f758560a2db870c1913 |
| turbo-cache-control | no-preview |
| go-import | github.com/triggerdotdev/trigger.dev git https://github.com/triggerdotdev/trigger.dev.git |
| octolytics-dimension-user_id | 95297378 |
| octolytics-dimension-user_login | triggerdotdev |
| octolytics-dimension-repository_id | 572570113 |
| octolytics-dimension-repository_nwo | triggerdotdev/trigger.dev |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 572570113 |
| octolytics-dimension-repository_network_root_nwo | triggerdotdev/trigger.dev |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 12fff95459b24b0f882a66698ee6a36a5934d247 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width