You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be good to have a comment in the build file with the version number, allowing to check whether an update is needed or no.
And it would be great if the website displays the latest version so that we can know about it.
Additionally, you might want to create tags for the 2.0.x releases in the repo, as you used to do for the 1.x versions.
The text was updated successfully, but these errors were encountered:
I've pushed up a commit that adds a version comment to the minified output file. I've also gone back and added tags for each stable release since (and including) 2.0.0.
I will update the website with version info when I release the next version (hopefully tomorrow).
@stof I'm not sure what adding the version number to the build file would do - it's already available in package.json (the standard file to check for such metadata). Would adding it to the build file (I assume you mean Gruntfile.js) be any more helpful to you? If so, I'm happy to add it.
It would be good to have a comment in the build file with the version number, allowing to check whether an update is needed or no.
And it would be great if the website displays the latest version so that we can know about it.
Additionally, you might want to create tags for the 2.0.x releases in the repo, as you used to do for the 1.x versions.
The text was updated successfully, but these errors were encountered: