Closed cryptoquick closed 10 years ago
This is actually an issue with the published builds. See here (this is where we are pulling these builds from). I will look into why they were not generated properly though...
I see... I was just concerned it might have been an indicator of a larger problem. If you believe it to be benign, that makes sense. That said, I didn't see this issue in the current build hosted here: http://builds.emberjs.com/beta/ember-data.js The issue must have been addressed at some point after the tag.
It is definitely a problem (and we'll figure it out), but this repo currently mirrors the published tagged builds for 1.0.0-beta.3. We need to get those builds updated/fixed and then I'll get this repo corrected.
I'll sit tight. :)
This has been resolved as of 1.0.0-beta.4.
Although this release is labeled by its bower.json as 1.0.0-beta.3, the source still says it's
'1.0.0-beta.2'
in the default, minified, and production versions. It appears the source has indeed been updated, as per 2ebef082c54ba1f07ae7b9a0d3fbbee7af8e9156 -- however, the version itself has, for some reason, stayed the same.