Well derp.  That was a bug that we relaunched from, and shouldn't have been made public.  It seems that didn't make its way into the git repository though.

I've pushed the update to git.  If you do a git pull - you should be good.  Sorry about that.