a day ago
Description
Currently, Railway's dashboard appears to deploy the latest commit from the connected GitHub branch, without providing an option to select a specific commit for deployment.
This limitation makes it difficult to roll out a particular known-good commit, test a specific revision, or deploy a previous version without modifying the branch or introducing additional workarounds.
Expected Behaviour
It would be helpful to have an option in the Railway dashboard to select a specific commit from the deployment history or connected Git repository and deploy that revision directly.
Use Cases
- Deploying a known-good commit without deploying newer, untested changes.
- Testing a specific revision in a production or staging environment.
- Redeploying an earlier commit when the latest changes introduce regressions.
Request
Could Railway consider adding support for selecting and deploying specific commits directly from the dashboard? This would provide greater control over deployments and make rollback and release management more convenient.
0 Threads mention this feature
4 Replies
a day ago
There's no option to pick an arbitrary commit from your repository and deploy it, but you can roll back to any earlier deployment. In your service's Deployments tab, open the three-dot menu on a previous deployment and choose Rollback (or Redeploy). Rollback restores that deployment's Docker image and custom variables. Redeploy builds it again from the same source code. Deployments older than your plan's image retention policy can't be rolled back.
You can also do the same rollback through the public API using the deploymentRollback mutation, as shown in Manage Deployments with the Public API. Thanks for the suggestion about picking a specific commit.
Status changed to Awaiting User Response Railway • 1 day ago
Railway
There's no option to pick an arbitrary commit from your repository and deploy it, but you can roll back to any earlier deployment. In your service's Deployments tab, open the three-dot menu on a previous deployment and choose Rollback (or Redeploy). Rollback restores that deployment's Docker image and custom variables. Redeploy builds it again from the same source code. Deployments older than your [plan's image retention policy](https://docs.railway.com/pricing/plans#image-retention-policy) can't be rolled back. You can also do the same rollback through the public API using the `deploymentRollback` mutation, as shown in [Manage Deployments with the Public API](https://docs.railway.com/integrations/api/manage-deployments). Thanks for the suggestion about picking a specific commit.
a day ago
That still doesn't fix the problem, I would really appreciate being able to deploy a specific commit at least given that some updates can cause breaking changes and the only stable version of the platform could be some 20 commits ago.
Status changed to Awaiting Railway Response Railway • about 23 hours ago
a day ago
The dashboard can't deploy a commit that was never deployed to the service. If the stable version you need was deployed at some point, though, it stays in your service's Deployments tab, however many commits ago it was. Open the three-dot menu on that deployment and choose Redeploy to build it again from that deployment's original source code and variables.
Rollback, which restores the existing image without a rebuild, only works within your plan's image retention window (72 hours on Hobby). Redeploy still works for older deployments outside that window. Thanks for the suggestion about choosing any commit from the repository.
Status changed to Awaiting User Response Railway • about 23 hours ago
Railway
The dashboard can't deploy a commit that was never deployed to the service. If the stable version you need was deployed at some point, though, it stays in your service's Deployments tab, however many commits ago it was. Open the three-dot menu on that deployment and choose Redeploy to build it again from that deployment's original source code and variables. Rollback, which restores the existing image without a rebuild, only works within your plan's [image retention window](https://docs.railway.com/pricing/plans#image-retention-policy) (72 hours on Hobby). Redeploy still works for older deployments outside that window. Thanks for the suggestion about choosing any commit from the repository.
a day ago
Can I get a human on this? This is a feature request. I am well aware of the current limitations of the Railway dashboard and would love for this addition to be made.
Status changed to Awaiting Railway Response Railway • about 22 hours ago