2 hours ago
Hello Railway Support,
We completed your recommended disposable-environment test successfully.
An explicit worker-only environmentPatchCommit with skipDeploys:true preserved the unrelated staged sentinel, including its patch ID, timestamp and SHA-256, after settlement. No deployment occurred.
Our real TLM staging environment now has 16 pending changes, including eight unrelated Amazon variables, one service creation and seven backup-worker fields.
The worker-only commit must include a pinned GHCR image, encrypted registry credentials and a JIT variable seal.
However, the Railway API masks these protected values.
How can we safely commit only the worker changes while preserving all unrelated pending changes and their encrypted values?
Please provide the exact supported API procedure. We must not apply the entire staged patch.
Thank you.
1 Reply
2 hours ago
We can't confirm that environmentPatchCommit with skipDeploys: true will apply only the backup-worker image, registry configuration and variable changes while leaving the other changes in that 13-change staged patch exactly as they are. Applying staged changes from the dashboard's Deploy action applies the environment's whole changeset, not just the selected service. There's also no per-change discard: Discard Changes drops the entire staged changeset.
Before you rely on this for staging, test the same sequence in an isolated environment that mirrors it: a staged patch with unrelated pending edits, plus the worker-only commit you plan to run. Then check that the unrelated edits are still staged afterwards.
Status changed to Awaiting User Response Railway • about 2 hours ago
Status changed to Solved kokaalbin-oss • 16 minutes ago