---
title: "Faster Staged Changes and Merges, More Tools for Bounty Hunters, Heroku White Glove Migration"
date: 2025-05-30
number: 0240
url: https://railway.com/changelog/2025-05-30-faster-staged-changes
---

# Faster Staged Changes and Merges, More Tools for Bounty Hunters, Heroku White Glove Migration

*Ok, let’s get to the final question in tonight’s episode of Who Wants to Be A Time Millionaire. *

*For $1M, can you tell us the ideal amount of time to wait for a merged commit to hit the Railway UI? *

*Is it …*

*A) 7 seconds*

*B) 7 minutes*

*C) 7 episodes of Survivor™*

*D) None of the above*

*… if you guessed D, CONGRATULATIONS! *

*The answer is none of the above — because waiting for your deploys to come through is the literal worst. *

If you’re like us out there and you were really starting to get annoyed by how long it was taking for deploys to come through to the Railway UI, then this changelog’s for you.

( Incidentally, this changelog is also for you if you’d like to learn how to save 40% on your Heroku bill — more on that below… )

Now let’s jump into it! 

## Faster Staged Changes and Merges

[Video: Whether you’re merging a staged change in the UI or merging a PR via GitHub, the experience is now much, much snappier]

We take a lot of pride in combining extraordinary distributed systems engineering with extraordinary UI performance.

So it was bothering us in a big way that it’s recently been taking way, WAY too long for some actions to reflect in the UI — specifically staged changes, GitHub pull request merges, and CLI merge commands like `railway up`.

So after a few long sessions of performance tuning, instead of up to 7 seconds of delay ( ☠️ ), you should now see updates hit the canvas in near-realtime. 

Whew. 

It’s [not the first time](https://railway.com/changelog/2024-12-06-multi-region-replicas#realtime-multiplayer-awareness) we’ve told you about our realtime performance ambitions, but it takes a lot of effort over many cycles to get where we wanna go. So stay tuned for more. 

Meanwhile, if there’s a UI experience that bothers you, we’d like to hear about it. 

Please make a ticket in [Central Station](https://station.railway.com/) or politely yell at us on [Twitter](https://x.com/railway). 

Onward!

## More Tools for Bounty Hunters

[Video: Want to be the first to know about a new bounty? Well we have a toggle for you!]

[Last week](https://railway.com/changelog/2025-05-23-bounty-hunt#bounty-hunters-rejoice-) we told you that some Railway community members are starting to make some *serious* coin on Railway through [Template Kickbacks](https://railway.com/open-source-kickback), [$1M for Open Source](https://blog.railway.com/p/1M-open-source-kickbacks), and [Account Referrals](https://docs.railway.com/reference/accounts#referrals).

We also re-introduced [Bounties](https://station.railway.com/bounties) in Central Station, which is a really exciting new way to get paid for your Railway expertise. 

This week, we wanted to point your attention to the `Subscribe to Bounties` toggle in [Central Station](https://station.railway.com/bounties), which will send you an email every time a new bounty opportunity drops — nice!

We also wanted to let you know that we’ll be giving away some [swag](https://shop.railway.com/) to the Top 5 Bounty Hunters over the next month.

Ok, that’s all from bounties, we’ll see you out there! 🫡

## Heroku White Glove Migration

[Image: We’re experimenting with a new campaign]

Would you like to chat with us about how to save 40% on your Heroku bill?

This is a little unusual for us to include in the changelog, but we thought you might be interested in a new mini campaign (above) and [landing page](https://railway.com/heroku) that we’re running. 

If you represent a company with production deployments currently on Heroku, we invite you to [book a session](https://cal.com/team/railway/migrate-from-heroku) with us. You can skip the landing page and book directly [here](https://cal.com/team/railway/migrate-from-heroku). 

Thanks and have a great weekend! 🌈

## Fixes and Improvements

- Some companies have requested that we add a way to require approval for every deployment in a workspace. We’ve added this feature by request. Please [open a ticket](https://station.railway.com/) if you need it enabled
- We updated some template URLs for indexing purposes