Hey @richplugins, you’re totally right. This could be causing a collection of issues.
The problem is I’m pulling in my dependencies via Composer and WPackagist. At some point, you changed how you were tagging releases. Rather than 1.4.2, you had tagged 1.42, but then eventually tagged 1.5, and then 1.5.1 and so on. 1.42 is technically a newer release than 1.9.1, and would get a patch release of 1.42.1.
I’ll update my dependencies to 1.9.x, which should get me the right version, but technically you would need to release 1.50 to be properly continuing along. If you end up needing to release a 2.0 at some point, that’ll also clear it up, heh.