That said, I think you should cut a 1.0.0 and use semver more seriously than I did in the past :)
All the commits we made since 0.2.4 were really bug fixes and code cleanup, so I thought it would be better to wait to bump to 1.0.0 so that the update would go out to anyone currently using 0.2.4.
>Nice work guys!
Thank you!
>That said, I think you should cut a 1.0.0 and use semver more seriously than I did in the past :)
All the commits we made since 0.2.4 were really bug fixes and code cleanup, so I thought it would be better to wait to bump to 1.0.0 so that the update would go out to anyone currently using 0.2.4.
Thanks @MoOx! It certainly feels like it could be a 1.0.0 with the amount of changes made and effort put in, and I'm all for using SemVer religiously from now on, but @BehindTheMath does make a good point about 0.2.4 users getting the update automatically.
That being said, 1.0.0 is a nice symbolic bump and 0.2.4 users can manually upgrade if there's a particular fix they've been waiting for...
Thanks @MoOx! It certainly feels like it could be a 1.0.0 with the amount of changes made and effort put in, and I'm all for using SemVer religiously from now on, but @BehindTheMath does make a good point about 0.2.4 users getting the update automatically.
That being said, 1.0.0 is a nice symbolic bump and 0.2.4 users can manually upgrade if there's a particular fix they've been waiting for...
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Nice work guys!
That said, I think you should cut a 1.0.0 and use semver more seriously than I did in the past :)
Thank you!
All the commits we made since 0.2.4 were really bug fixes and code cleanup, so I thought it would be better to wait to bump to 1.0.0 so that the update would go out to anyone currently using 0.2.4.
Thanks @MoOx! It certainly feels like it could be a 1.0.0 with the amount of changes made and effort put in, and I'm all for using SemVer religiously from now on, but @BehindTheMath does make a good point about 0.2.4 users getting the update automatically.
That being said, 1.0.0 is a nice symbolic bump and 0.2.4 users can manually upgrade if there's a particular fix they've been waiting for...
I've added a couple of extra changes to the log, based on PRs made between now and 0.2.4, but otherwise I think we're all good to go!
Version 0.2.5 has been released to NPM.
Fantastic, nice work all! 🎉