Sugar, spice, and… dead bugs? WD-40 branded anti-rust solution? 

We’re sweetening up the platform as of late but we wanted to make sure that it runs smoothly as well. This week has been a polish week as we prepare for larger features and launches coming down the pipe. As such, some of the team is taking some RnR to recharge and refuel for the next round. 

That being said, we hope you enjoy these few updates and enjoy the last weekend of August.

 for all services that are using the new edge proxy. As mentioned last Changelog and demanded from our users. This week we’ve added the ability to filter those logs on the deployments page.

More of you have put Railway in places we never expected: and we’re not talking about GitLab. 

Brody and JR collaborated for the jam of a 

 week with community member Maddsua to make sure that the Railway CLI works in your build flows.

 now works in CI environments much nicer now. CI environments are automatically detected and the deployment status is streamed and terminated as soon as the build passes or fails. No more hacks. 

A few Changelogs ago we announced native Slack Connect integration within Railway. We then shipped Slack Support that ties directly into 

We’ve now crossed 100+ Slack Support queries handled natively within Slack. While Chandrika is running the numbers on our stats we’ve decided to prevent further dropped balls. 

Customers expressed confusion when they needed to type 

 - imagine you facing an issue and then forgetting how to ask for help. We regret the error.

Now, in our Slack Connect channels, we will assume all questions are help threads and will auto-thread appropriately. 

For this to work properly, you’ll need to link your account to Slack.

 Our bot may have gotten a bit naggy to enforce this, but we’ve been able to bring quick resolution and finality as a result to our customers.

Keep in mind: if you have workloads deployed, you can spin up a Slack Connect channel via the Team Settings page!

A few weeks ago we asked you to share any nits of the platform that you have with us in a 

. We’ve been closely following it and tracking all those requests internally. We just wanted to provide an update of the things that we’ve fixed/addressed so far. Please keep the nits coming!

Shared variables UX improved around deleting and editing variables

Improved deployments list initial and exit animations

Fix GitHub deployment detection in the UI

Handle failures to deployment draining and ensure that old deploys are still cleaned up

Improved automatic Slack channel creation for teams, we will no longer only invite a subset of the team. (Sorry, if we made anyone feel excluded.)

Strong(er) TLS security on Railway domains

Better logs when failing to create a service via the public API

Better errors when failing to checkout a GitHub commit

Prevent direct node overlap in the canvas

Fixed a UI crash if you opened and closed the side panel details pane

Addressed an issue with the new proxy when dealing with different compression types from user workloads

Rolled out an improved workload orchestration engine

Added links in the footer to make contacting the team easier (useful for Sales convos)

Added a Service selection option in Help Station to make it easier to report issues

Accessibility improvements for rendered text in dark mode

Accessibility improvements for colors on graphs in the observability pane for users with color blindness

Improvements to deploy status communication on the deployment pane. Deploy stages should be 99.99 percent accurate now and should no longer lie to you.

Fixed the prepaid payment flows for certain card types. 

We think the above Nits Thread highlights all those fixes we’ve been up to this week. 

However, we do want to address an operational improvement we put in place to prevent an outage like the one that occurred on August 27th, 2024. 

You can read the full incident report on our blog.

https://res.cloudinary.com/railway/image/upload/v1725074337/2024-08-30_qf45lo.png

HTTP Log Filtering, Slack Support Auto-thread, The Nit Squash

Changelog #0201