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
make versionned releases #8
Comments
Sorry. Yes, you are right. I was too lazy so far. But in future i will version a bit more. But that would mean you will have to rely on tags instead of the head of master. Is that okay for you? |
I have created two tags now. Current version is 1.0.0. The latest working version before i changed and added a lot of API calls is v0.1.0 |
Not sure what that means, but that's pretty much what i want i think. :)
Thanks!
I have done something for this in Wallabako. In the makefile, I have:
and in the source:
then i can just use that as a string... I wouldn't commit the version number in Git, that's just asking for trouble... |
I think this does not work for a library because it is compiled as depencency and the makefile does not get executed. I am going to use this method for my wallabg-stats binary |
true, not sure how that's done with libraries... |
i think this can be closed - you tagged releases, thanks! :) |
i do not like the "v" in the tag name anymore. In future tags are coming without that, but old tags are still valid, too. |
hello again! :)
i was surprised to find an API change when my CI failed here... Turns out that GetEntries now needs a callback, which is fine, but i didn't expect such a change without a version number bump.
i encourage you to tag releases and use the semver.org standard for naming those versions. if there would have been a major (or even minor) version bump I would have been more careful before doing my own releases...
The text was updated successfully, but these errors were encountered: