Happy Friday- another week of shipping, shipping, and more shipping. One last piece of house keeping; we do expect to make NixPacks the default builder for new projects next week. No changes on your end will be needed.

Members of teams should see additional information like seeing who is in your team and your status within the team its self.

Along with this change, our designer, Jitachi could spare no detail. We now have improved team empty states and taller project cards for improved readability.

Let’s be honest, our healthcheck system previously had some, uh… room for improvement. So, we spent this past week making it better 🪄

Healthchecks now run instantly, no longer adding ~30 seconds of overhead

Build Logs now include detailed healthcheck failure logs

Deploy logs are now available for failed deployments, allowing healthcheck debugging

 If you’ve ever accidentally deployed some bad code to production—something we’re all guilty of—you should try them out. Simply set the healthcheck path in your service settings and Railway will fail any deployment that doesn’t respond with a 

We want Railway to be one of the best ways to deploy software- and you can’t do that without good versioning. Historically, vendoring has been a little bit of a challenge with starters because we only allowed the option to deploy from the main branch of the repo. 

Now, upon successful deployment of any service within a project linked to a template, we create a version of that service that contains the 

 of the commit and the title of that commit that was deployed as the content.

This version becomes selectable within the starter deploy UI for users to choose. If users need to use an older or experimental version of your starter deployed? A dropdown is present giving your users control on what version to deploy.

This is one step towards fully reproducible infrastructure on the platform and we feel that this is a massive improvement over the status quo. Have a starter you wanna make? 

It’s easier than ever, with our template flow.

Certain log lines no longer incorrectly inherit the color of other logs

Fix an issue with the verification page that mistakenly confused users with a invalid GitHub where it was valid

Shipped NixPacks v0.1.0, now with full parity on Heroku Buildpack support

Our fight against spectres continue, added more tooling for us to spot and kill phantom deploys.

https://res.cloudinary.com/railway/image/upload/v1657322171/og-images/better-healthchecks_o5pgjg.png

Dashboard Improvements, Better Healthchecks, and 

Changelog #0087