This week we’re talking about Staged Changes and Environment Syncing — two features that have been totally overhauled in preparation for today’s General Availability release.

We’re also bringing you a final reminder to 

, as well as an all-new Production Readiness Checklist, and a new Community Forum Leaderboard. 

Staged Changes is now available to all Railway users!

Staged Changes brings a sensible workflow to making batch updates to your projects

 lets you stage one or more changes to your services and environment, then review them, then commit them all at once. This feature is designed especially for working with larger projects across multiple services.

As you create or update components within your project, the number of staged changes to your project will increase.

Then when you’re ready, you can hit the 

 button (and optionally append a commit message) and the change will appear in the activity feed. This also lets you see what changes were made when and by who. Nice!

We’d love your feedback on Staged Changes — visit the 

Environment Syncing is now available to all Railway users!

Environment Syncing makes it easy to make structural changes to your projects

The tl;dr is that we’ve taken the best parts of the previous “Fork/Merge Environments” feature set and integrated them better into Railway as Environment Syncing.

These new flows make working with PR environments and a large number of contributors much easier. 

When creating a new environment, you can now either start from a blank canvas or duplicate an existing environment.

Once you make changes to your new environment, you can sync changes across to your production environment. You can even discard entire service changes and only pull in the changes you want.

Note that forked environments no longer exist. If you’ve already created one or more forked environments, they will behave like regular environments. You can sync the changes to any environment instead of merging them only into the base environment.

We can’t wait for you to get started with Environment Syncing! 

This is the very last time we will remind you to upgrade your plugins. 

All migrations must be completed by January 31, 2024

We fixed an issue with disk pricing on the product usage page

We fixed some styling issues on the Template deploy page

We added checksuites to the new service settings UI

We fixed some broken links in the Community Forum

https://res.cloudinary.com/railway/image/upload/v1706319069/2024-0126_ldh0vq.png

Staged Changes Generally Available, Environment Syncing Generally Available, Last Chance to Migrate

2024-01-26-staged-changes-generally-available

Changelog #0170