It [seems](https://github.com/elasticsearch/kibana/blob/master/Gruntfile.js#L194) their distribution process only provide the latest code and does not archive specific commits or tags. An alternative would be to manually repackage the code ourselves using their provided `Gruntfile`, either when provisioning or as our own Jenkins type job elsewhere - the build process requires node/grunt/other modules. Most likely, they'll eventually move to a similar scheme as they do with elasticsearch downloads where the tagged versions remain archived. In the meantime, I suppose they believe the project to be too hot for that to be worthwhile? Until that time, I think it might be better to stick to downloading from GitHub and just using the non-minified form so we can lock on a version.

Any further thoughts, @mrdavidlaing?