Hello @Cvmcosta! 👋
First off, thank you for maintaining this awesome library. I’ve noticed a small inconsistency between GitHub releases and npm:
GitHub’s last release: 5.6.5
npm’s latest release: 5.6.9 (with versions 5.6.6, 5.6.7, and 5.6.8 missing on GitHub and npm)
There are also several missing or untagged versions in the repository.
Would it be possible to ensure that each release is tagged and published on GitHub so we can keep a clear and consistent release history? ✨
Additionally, I’d love to suggest using Conventional Commits or a similar semantic versioning workflow to streamline release management. Something like release-please could automate the tagging and changelog generation for future releases. 🚀
I’m more than happy to help with any of this if needed—just let me know! 🤝
Thanks again for your hard work.
Hello @Cvmcosta! 👋
First off, thank you for maintaining this awesome library. I’ve noticed a small inconsistency between GitHub releases and npm:
GitHub’s last release: 5.6.5
npm’s latest release: 5.6.9 (with versions 5.6.6, 5.6.7, and 5.6.8 missing on GitHub and npm)
There are also several missing or untagged versions in the repository.
Would it be possible to ensure that each release is tagged and published on GitHub so we can keep a clear and consistent release history? ✨
Additionally, I’d love to suggest using Conventional Commits or a similar semantic versioning workflow to streamline release management. Something like release-please could automate the tagging and changelog generation for future releases. 🚀
I’m more than happy to help with any of this if needed—just let me know! 🤝
Thanks again for your hard work.