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'm using this library in quite some projects. To guarantee that those projects never break the integration with this library, it would require them to trust that the API of the library will not change. By having version tags (git tag), we would be able to point to those tags instead of relying in an unstable master branch or fixed commit shas.
It would be possible if you start tagging versions with semver?
Thanks.
The text was updated successfully, but these errors were encountered:
I'm using this library in quite some projects. To guarantee that those projects never break the integration with this library, it would require them to trust that the API of the library will not change. By having version tags (
git tag
), we would be able to point to those tags instead of relying in an unstablemaster
branch or fixedcommit shas
.It would be possible if you start tagging versions with
semver
?Thanks.
The text was updated successfully, but these errors were encountered: