alexbrainman
commented
2 years ago @rchapin thanks for creating this issue.
But I see no benefits of adding git tags to this repo.
When I use this package in some code, I just use git commit hash to refer to a version of this package. And once commit hash is added to go.mod file, it remains there forever.
This code also does not change over time. So I find using master branch for all my projects suitable.
Perhaps your situation is different. So please tell more.
Thank you.
Alex
Most go projects add tags at various points in the development so that consumers of libraries can guarantee that they are getting a specific version that they know works with their code.
This project looks interesting and I was going to use it, however the fact that every time I build I am pulling from master and just hoping that nothing has changed that makes it incompatible with my application is a deal-breaker for me.
Please consider adding tags for stable versions of the library.