You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have version 0.2.8 installed from a week ago.
I saw there is a new commit 4 days ago - which I installed
It is still tagged 0.2.8 - so the version ID is no longer a reliable indicator of version.
Please make sure that the version ID is always updated when making a new commit ot master branch. the conventions is
major.minor.patch where
major = breaking change or major release.
minor = new feature that is not breaking
patch = bug fix or other change that does not introduce a new feature/function.
So I'd suggest we move to 0.3.0 now and then start incrementing the patch number every commit unless there is some new feature.
The text was updated successfully, but these errors were encountered:
I have version 0.2.8 installed from a week ago.
I saw there is a new commit 4 days ago - which I installed
It is still tagged 0.2.8 - so the version ID is no longer a reliable indicator of version.
Please make sure that the version ID is always updated when making a new commit ot master branch. the conventions is
major.minor.patch where
So I'd suggest we move to 0.3.0 now and then start incrementing the patch number every commit unless there is some new feature.
The text was updated successfully, but these errors were encountered: