New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
proper releasing #45
Comments
@gustavoFreireS, do something about it, please, I'm having to read the code and commit messages to follow which version introduced the features I wanted. Probably anyone (but another core contributor) will do the same and will likely just stop using the lib. |
also, there are many versions being skipped (and only having their alphas) |
Use semantic-release to change the version automaticlly closes #45
Use semantic-release to change the version automaticlly closes #45
🎉 This issue has been resolved in version 0.4.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
current releasing flow is kinda sloppy and there's no changelog nor git tags whatsoever besides this old "Release History" section on readme file.
if everybody agrees, we could remove this old section from readme and start using
npm version
(https://docs.npmjs.com/cli/version) like true ladies/gentlemen (and only atmaster
would be nice), possibly using github's releases tab for changelog.also: https://semver.org/
The text was updated successfully, but these errors were encountered: