failed to solve: secret X not found is buildkits real error for a --mount=type=secret,id=X line with no value, and railway only sets RAILWAY_GIT_REPO_OWNER when github is connected, which yours isnt. can you paste your dockerfile (or confirm if youre even using one)? want to check if it references that secret directly before saying for sure where to remove it

I got same problem. Posted here: https://station.railway.com/questions/railpack-builds-fail-with-secret-railwa-575304cf

I'm not using a Dockerfile. The services use Railway's Railpack auto-detection for Python, and I'm deploying local source with railway up.

The build gets as far as Railpack 0.36.1 generating/loading railpack-plan.json, then fails at install mise packages: python with:

failed to solve: secret RAILWAY_GIT_REPO_OWNER not found

I can reproduce the exact same error on two different services (oauth-web and retention-cleanup) in the same project.

The project isn't connected to GitHub. So if RAILWAY_GIT_REPO_OWNER is only available for GitHub-connected builds, could Railpack 0.36.1 be incorrectly referencing that secret for CLI/local-source builds?

Hey, The fix is rolling out, Can you try redeploy your service?

im having same issue Build Failed: build daemon returned an error < failed to solve: secret RAILWAY_GIT_AUTHOR not found >