Bump version number.

[josephdburdick]

This simply matches the .js file number with the release number to avoid confusion. Also, while version 1.6.2 is the latest version since last November the only version available on Bower is 1.6.1. I'm not sure which version addresses this because of the version mismatch but:

When I download your plugin from Bower I get a .bower.json file that lacks a "main" key which means when trying to use Browserify it can't find the actual JS file. The solution in my eyes is to make a new release from 1.6.1 to 1.6.2. Perhaps this will carry over the change you've already made and update it on Bower.

[josephdburdick]

Can confirm, after I forked this and created my own release I was able to access the proper bower.json information you already have in place. Please make a new release on Github so people pulling via Bower can get the updated info which improves its modularity for Browserify and the like!

[adamwulf]

Thanks!

[adamwulf]

just posted a new release as well pointing to this commit. I'm not a bower users, so lmk if this didn't do the trick for some reason

[josephdburdick]

Awesome, I'll switch over to yours tomorrow when I return to my desk!
And for the record, this doesn't just bode well for bower users, I'm using Universal Modules to load your plugin as a shim. This is very helpful for writing JS modules and soon with ES6 is prevalent it will be standard. Thanks @adamwulf!