We've updated the create project from repo flow. You can now optionally add variables before the project is created. The entire process is also received a fresh coat of paint and looks much nicer (thanks to our amazing designer).

Railway uses a special secret sauce to determine if users can be considered trustworthy enough to deploy on our platform. 

We have this in place to prevent abuse, and we make it so that our systems have good fallbacks in case if it fails well-meaning new users with a newly created GitHub account. 


Account verification will be required to get account credits, and in the possibility that we might get it wrong- there is now an integrated appeal form to make it right.

This isn't the flashiest of features, but we figured it is worth highlighting as some of you may run into it. We've improved our automated repo detection and will prevent projects from being deployed if we detect they are using a banned dependency. This should improve the Railway experience for everyone since the usage of these dependencies would eat a lot of the resources on the free plan clusters and we've seen increased stability after rolling out this change.

 from brew formula that was causing errors 

https://github.com/railwayapp/cli/releases/tag/v0.2.47

Healthchecks now retry a few more times to ensure the proxy has a chance to update

 will not crash if the directory has symlinks

https://user-images.githubusercontent.com/3044853/140593123-0a83440e-6ad0-4df9-b873-92dcd9cd4ec4.png

Smoother Create from GitHub and Verify Changes

Changelog #0054