This was a bug in the build process and has been fixed now. Thanks for reporting!