It's fixed.
(Sorry we didn't catch this sooner, it was a rather obscure build publishing issue: our internal builds were fine, they just weren't getting published.)
(Sorry we didn't catch this sooner, it was a rather obscure build publishing issue: our internal builds were fine, they just weren't getting published.)