Skip to content
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

Please tag releases and track changes #213

Open
beruic opened this issue Aug 11, 2021 · 1 comment
Open

Please tag releases and track changes #213

beruic opened this issue Aug 11, 2021 · 1 comment

Comments

@beruic
Copy link

beruic commented Aug 11, 2021

I am currently in doubt whether I should upgrade from 1.3.1 to 1.4.0 because I have no way of assesing if there are any breaking changes.
I releases were at lease tagged, i could look at a diff of the two versions. Optimally there would also be releases here on GitHub stating the changes.

@cozmo
Copy link
Owner

cozmo commented Aug 24, 2021

We follow semantic versioning, so there should be no breaking changes between those two versions, as it's a minor not a major change.

Adding tags to correspond with npm versions is a good idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants