We're currently aware of this issue.
In fact, it's caused due to a change that was expected to happen in the API not being there yet (it'll be fixed soon)
And yeah, I was the one that opened that fateful PR on the bot's repo, so I'm kind of the one that caused it? o((>ω< ))o (whoops)