Closed marcusmoore closed 9 years ago
It seems you are correct. Packagist says "The easiest way to manage versioning is to just omit the version field from the composer.json file. The version numbers will then be parsed from the tag and branch names."
Looks like there was a version bump but it wasn't tagged correctly?
Packagist only shows 1.0.0 as well.
As a side note: the issue here said that he had to manually pull in the migrations. I believe this is because publishing the migrations were added in 1.0.1 which is available for download.