Welcome to another weekly Railway changelog.
Monorepo Support
Railway now supports monorepos. This means you can run railway init at your
project root and connect to the same Railway project in any of your sub-packages
(e.g packages/frontend). We've also removed the .railway directory that we
created in your project when you ran init. Don't worry though, we will migrate
your project automatically when you run railway run.

Upgrade now with Brew or NPM
npm i -g @railway/cli
# OR
brew upgrade railwayDeploy Links
We've been hard at work rebuilding our deployment engine. It's now more durable, fault tolerant, and quicker (~10s to deploy a bare app). Additionally, https out of the box.
We've aiming to have it GA for next week, but as always, you can reach out via the Discord and we'll turn it on for you.
On the UI side, we've added deployment links to the dashboard. When a deploy is successful, you've be able to click "Success" and it'll open an external link to your deploy.

And More!
Along with the above we have also added a few bug fixes and quality of life improvements.
- Fixed bug that prevented some from logging in with GitHub when they had no email set
- Fixed issue where some deployment builds would fail
- Fixed a font rendering issue on BigSur
- Improved UX of project invite page
- Fixed an issue where the CLI configuration file sometimes wouldn't be created