Open zxp19821005 opened 12 months ago
Agree. I think that requires some changes, for example in translation is a fixed word "(Latest)": " but of course is very helpful to have a version number, users think to have the latest version and it well could be that is not.
That would require a tagged/versioned release, however, there hasn't been one, hence why it is always latest. i.e. it's a discrepancy between it being a tagged release, and the version that was manually set in https://github.com/EdgeTX/buddy/blob/main/package.json
@pfeerick should we start incrementing the release numbers and have some proper "releases"? It would probably make sense for downstream packaging.
No complaints from the peanut gallery... especially if it makes the lives of potential contributors or other package maintainers better ðŸ¤
I'm happy to implement automated versioning. I've done this before using semantic-release which will auto increment the version number on merge to main depending on the conventional commitments which were merged to main
I've put this off because originally the project was considered a prototype and didn't want to spend time thinking about versioning
I'm happy to implement automated versioning.
Sounds great :-) Let do it!
Where did this end ?
Where did this end ?
Nowhere for now 😅
Will you please add the correctlly version of the package? It's always 'latest' now. I've ported the package to AUR edgetx-buddy-bin , but the version was always '0.1.0'.