4 hours ago
Hello Railway Team,
We use Railway Pro for a Medusa e-commerce staging environment.
We currently have 16 uncommitted staged changes that must remain untouched.
We want to deploy one specific GitHub commit using:
serviceInstanceDeployV2(serviceId, environmentId, commitSha)
Could you please confirm:
- Does this mutation deploy only the specified commit without applying, consuming, rebasing or modifying existing staged environment changes?
- Will the original staged patch ID, contents and
updatedAtremain unchanged? - Does the same guarantee apply when the staged changes include variables
1 Reply
4 hours ago
serviceInstanceDeployV2 with commitSha starts a new deployment of that commit for the one service, after checking the SHA against the connected GitHub repo (an unknown SHA returns "Commit not found" and creates no deployment). Staged changes are applied through a separate action, environmentPatchCommitStaged in the API or Deploy on the staged-changes bar in the dashboard. Clicking Deploy on that bar applies all staged changes together.
We can't confirm whether the deploy mutation leaves the staged patch's ID, contents and updatedAt exactly as they are, including staged variable changes. We also can't confirm whether staged variable values are excluded from the new deployment.
If your workflow depends on that, test it first in a separate environment with a few staged changes, including a variable. Read environmentStagedChanges before and after the deploy and compare the patch id, updatedAt and patch contents. You can request patch without decryptVariables so variable values stay encrypted. Reading staged changes doesn't apply or deploy anything.
Status changed to Awaiting User Response Railway • about 4 hours ago
Status changed to Solved kokaalbin-oss • about 3 hours ago