Happy Easter to all who celebrate 🐣. This week the team worked on improving some existing workflows and hardening the platform. We also put extra thought and care in helping our community be sustainable.

 experience has been completely reworked. We could talk all day about this flow and the amount of work that went into making it feel s m o o t h, but why don’t you just check it out yourself 👉 

The team was hard at work making sure the Discord is a welcoming place for developers new and old. The server just passed 3,000+ users and we are setting the foundation for the next 10,000+.  We have added new roles called Onboard and Verified Account. 

(With a tiny Twitter themed easter egg.) 



Those who linked their Discord Account to Railway may need to re-link their account to get the new Verify Account role.


We have also added additional on-boarding steps, new members will need to react to join the community. To be clear, we didn’t say you had to write React.

We now require your Railway account to be in good standing before you can link your Discord account. You will now be required to link your account to Discord if you wish to post a support thread on the server.

This is part of an ongoing effort to curb abuse and spam on the server to keep support response times quick.

Render JSON data correctly in SQL query view

Fixed issue where repos were not loading for some users

Fixed issue where logs would sometimes not appear

Project ID is now required to open a support thread

https://res.cloudinary.com/railway/image/upload/v1650069879/docs/Newer_Dev_New_v7hyy5.png

Newer Dev.new, Community Updates, Discord Link Account Requirements

Changelog #0077