Hello again! The theme of this changelog is "visibility" and boy do we have some cool stuff for y'all this week.

Background: Many people were asking for a redeployment button in the UI. It's probably our #1 request. We REALLY appreciate the feedback, but we believe this to be an antipattern. 

A deployment shouldn't be something that's manually triggered, because that introduces an issue where you might leave a ticking time bomb around, a redeployment happens, and everything breaks.

Instead, we will now automatically redeploy any GitHub triggers after the variables for an environment changes (up deploys are not redeployed). This means no more README updates to trigger a deploy after you edit an environment variable!

Metadata about who fired the deployment (if via CLI), or which commit triggered a deploy (if via Git) is now included in the deployments view

Another ask we've seen quite commonly is, well, it's not even really an ask it's "I forgot to setup my env vars for prod but I did it in dev D:". We're hoping this will ease some pain, especially coupled with the auto deployments feature.

If a variable is missing, we'll notify you and allow you to import it across environments. Check the example below!

Fix: Fixed a bug in the routing layer where sometimes http services would be registered as TCP, causing bad gateway errors

Fix: Better handle routing when te project unique name is changed

https://user-images.githubusercontent.com/3044853/107821680-cabdc380-6d74-11eb-9262-74fd93585d1d.png

Auto Redeploys, Deployment Metadata, and Variable Warnings

Changelog #0016