🎉 Welcome to this week’s edition of the Railway Changelog! 🚀

As we dive into the first full work week of the new year, it’s been all hands on deck at the station, planning, mapping out the 

features and improvements we’re excited to bring you this quarter.

But first, let’s take a moment to highlight what we shipped this week! 🚂✨

We have added the ability to add pre-deploy commands that handle tasks such as database migrations, data seeding before your app runs. This can be added in the 

These commands will be executed within your private network and have access to your app environment variables.

 It is important to note that the deployment of your app will fail if the pre-deploy command fails!

At Railway, we’re committed to making migrations effortless, ensuring you can transition to our platform with little to no effort while reaping all the benefits.

Now, migrating your apps from Render is easier than ever. Simply use the 

 option, and Railway will automatically detect your 

 file. From there, our platform will handle the creation of all necessary services and variables for you.

For a step-by-step walkthrough, check out our 

We worked on enhancing the speed and overall performance of multi-region deployments.

By optimizing the way the multi-region deployments happen on our platform, we have ensured that your applications can scale seamlessly across different regions. This means your users can enjoy a smoother, faster, and more reliable experience, no matter where they are in the world.

Attaching a volume to a service in metal will switch that service to non-metal.

Logs will be anchored to the bottom when new logs come in.

Allow scrolling in the data UI side panes.

Better errors when the image being deployed was built for the wrong architecture.

Fixed a bug that caused 2FA checks to happen any time a volume in a non-default region was used.

CLI: Fixed an issue when installing with bash that would fail if a new release was in the process of being created.

CLI: Fixed hanging of --ci option if deploy was skipped because of watch patterns (thanks 

CLI: Fixed railway login showing as failed in the Railway dashboard even though it was successful

https://res.cloudinary.com/railway/image/upload/v1736550184/docs/quick-start/2025-01-10_pm8f6x.png

Pre-deploy Command, Migrate Render apps, Faster Multi-region Deployments

Changelog #0220