We’ve been able to replicate the problem and have pulled the 2018.5.0 release for now. It appears to be related to what should have been a minor change to reduce the number of API calls we make in building the release screen, we have a few engineers paired up and working on the problem now.

We will get a fix completed as soon as possible and included it in 2018.5.1 which we will release as soon as this fix is ready and tested (which should be in the next few hours).