9 days ago
I'm preparing a controlled database credential rotation for an existing Railway production service. Before proceeding, I need clarification on two Railway behaviors.
1. Builder compatibility
The approved Git commit specifies builder: NIXPACKS in railway.json, but Railway's live service configuration reports RAILPACK.
Can Railway safely build and deploy that exact unchanged commit? Which builder configuration takes precedence, and is any migration or configuration change required?
2. Empty staged patch
One Railway status interface reports an older EnvironmentPatch with zero changes, while the staged-changes interface reports no pending changes.
Is this empty patch inert, or must it be resolved before a new staged deployment? If resolution is necessary, what is the supported procedure?
The intended maintenance will stage a specific Git commit and a replacement database variable together, then apply once.
Please confirm the supported behavior. This is a request for guidance only; please don't change or deploy anything.
1 Reply
9 days ago
On builder precedence, settings in your railway.json override the service's dashboard settings for each deployment. The dashboard values are never rewritten to match the file, so it can keep showing RAILPACK. The deployment details page marks each setting that came from your config file, so after a deploy you can see which builder that deployment actually used. Our current config reference lists only RAILPACK (the default) and DOCKERFILE as builder values, and any Dockerfile found in the repo is always used for the build. We have not confirmed how a NIXPACKS value is handled on today's build path, so we can't promise that this exact commit builds the same way it did before.
Config as Code (railway.json / railway.toml) is also deprecated. Existing files keep working only until 2026-12-01, so plan a move to Infrastructure as Code before then.
On the staged patch, we checked this environment's staged changes and found nothing pending. We have not established what the older zero-change patch in the other status view is, or whether it has any effect on a new staged apply. We have not changed or deployed anything.
Status changed to Awaiting User Response Railway • 9 days ago
2 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 2 days ago