Rolling back to the revision before @heroku's silent breaking update at least gets me a proper error message.