Closed danibix95 closed 2 years ago
Hello @danibix95, it was a typo on my part 😅 There's no breaking change. I'm trying to unpublish the version and release a v2.5.3 instead.
Yes, clearly, my next goal is to improve the release cycle to avoid those typos, and keep a clean changelog. I think I'm gonna use GitHub releases for that.
Ok, thank you for the clarification @ThomasAribart
Github releases are also perfectly fine, even though they are not platform agnostic.
I believe this issue can be closed as soon as next release is published.
Hi @danibix95 ! v5.2.3 has been unpublished and v2.5.3 is now available 👍
Hi,
thanks for your work! I noticed that the repository has just been updated to its latest version, moving it from
v2.5.2
tov5.2.3
.Would it be possible to provide a
CHANGELOG.md
file, similar to the one proposed in keepachangelog website to briefly explain the changes that are introduced with each new tag?Moreover, would it be possibile to describe the reason why repository version moved of three major versions? Is it possible that is just a typo?