This week you’ll notice that the Railway Changelog is being posted … on a Monday! As Railway production deployments ramp up massively (see below), we felt it was time to start reaching you during the work week. 

We’re planning some pretty cool new improvements to feature updates, so this is the first of a few changes to the Changelog that will come your way. 

Don’t worry, we’ll still ship code on Fridays. 😜

We released Config as Code to Priority Boarding Passengers four weeks ago and the reception has been 

. We couldn’t wait to get this feature into GA. 

If you need a refresher, Railway now supports defining the configuration for a single deployment in a 

It finally happened — we deprecated Heroku Buildpacks in favor of 

. This means it is now impossible to switch your builder back to the legacy buildpacks.

If you have a service using Heroku Buildpacks or Paketo Buildpacks, you will see a dropdown menu giving you only one option: Nixpacks.

In the last few weeks, we’ve fixed a number of build issues with PHP and Ruby. We also used this time to add quality of life improvements within the platform when it comes to builds.

Since we no longer need to support three sets of build tools, we will use our new bandwidth to invest more in Nixpacks tooling and documentation. Thanks for bearing with us through this transition! 

We reached 2M builds just four months after reaching 1M builds. Let’s go! 

At this rate, we’ll reach 8-figure builds soon enough. Thank you for your continued support. ❤️

Improved the look and feel of dropdown styles in the UI

Improved responsive design for Project Settings page

Completed migration to new email sending provider

Fixed a bug that sometimes caused issues with Shared Variables in the UI

https://res.cloudinary.com/railway/image/upload/v1669013652/docs/heppy-2-million_xstvgq.png

Config as Code to GA, Heroku Buildpack Removal, Celebrating 2M Builds 

Changelog #0108