Hi Railway team,

Deployments from the Railway CLI are consistently failing during the Railpack build stage with:

Build Failed: build daemon returned an error < failed to solve: secret RAILWAY_GIT_REPO_OWNER not found >

This appears to happen before the application is built or started.

What I have verified:

• Environment: staging
• Deployment method: railway up
• Railway CLI: 5.37.3 (Homebrew)
• Railpack: 0.36.1
• Python detected successfully by Railpack
• The failure occurs at install mise packages: python
• The same error occurs across multiple services in the same project.
• I reproduced it on both oauth-web and retention-cleanup.
• Existing running deployments remain healthy.
• No application/database/environment changes are required for the failure to occur.

Relevant build log:

scheduling build on Metal builder "builder-iiwzrh"

using build driver railpack-v0.36.1

↳ Detected Python

↳ Using pip

...

install mise packages: python

Build Failed: build daemon returned an error < failed to solve: secret RAILWAY_GIT_REPO_OWNER not found >

I retried the oauth-web deployment and received exactly the same error, then tested a different service (retention-cleanup) and reproduced the same failure.

Could you please check whether RAILWAY_GIT_REPO_OWNER is expected to be injected internally by Railway/Railpack, and whether there is an issue with the build metadata/secrets for this project or the Metal builder?

I have not manually created a RAILWAY_GIT_REPO_OWNER variable because it appears to be Railway-internal metadata.

Project ID: d1b95395-d34d-4bea-8b1a-123b00de6b6a

Failed deployments:

• oauth-web: cca467d0-1f1d-4b4a-b681-ea8687517b7f
• oauth-web retry: c09777af-5e57-4dbd-b26e-11042e8f662a
• retention-cleanup: 13de2ca2-8512-4266-92eb-27cca30d0966

Thanks.