Closed odysseuscm closed 8 years ago
@odysseuscm works for me...
I get
this.MooTools = {
version: '1.6.0',
build: '529422872adfff401b901b8b6c7ca5114ee95e2b'
};
can you provide more info (browser, os)?
That was a mistake, and it's fixed now.
Something went wrong with tagging the release, so we ended up creating the tag later. Apparently we didn't re-fetch the repository on the web server for it to know about the tag, and it got stuck on master
, rather than retrying.
The commit master
referred to was 1.6.0 + 1, so there is no actual functional difference, the only difference is the version number in the file: https://github.com/mootools/mootools-core/commit/2f0aee54c40525e4261b556bc6ed2a12a619db73
I see, thanks!
Thanks for reporting! :+1:
Thanks for fixing @timwienk, the wrong release tagging was one me. Sorry for that.
Hi, all core/more downloads on mootools.net, including the ones generated by the builders send out 1.6.1dev instead of 1.6.0. Is that by design or a mistake?