Playwo
Add suffix to version without it showing up as a prerelease
But now that I read the description for build metadata in the version (behind the +) I think that makes the most sense semantically as well
Thus two versions that differ only in the build metadata, have the same precedence
There is a testnet and a mainnet for each package so it could be useful to have both
1.1.0-gaia-v15.1.0
and 1.1.0-gaia-v15.0.0
around with no precendence as these are both the latest for their repective network28 replies
Add suffix to version without it showing up as a prerelease
e.g. for gaia I could just go to their github repo, check that the latest release is v15.1.0 so I know that the package is compatible.
If its just 1.0.0.65 I'd need to go to the Cosm.Net repo and check which commit the submodule is checked out to
28 replies
Add suffix to version without it showing up as a prerelease
I see makes sense. I could use an underscore instead of a dash to get around it I guess 🤔
https://i.imgur.com/eUTRCI4.png
28 replies
Add suffix to version without it showing up as a prerelease
To give some more context, even tho people tend to hate it. These are blockchains, the code is often released ahead of time and the actual chain is updated later on and exposes a new version of the API from there on.
Hence build dates make very little sense
28 replies
Add suffix to version without it showing up as a prerelease
Well I would use
Major.Minor.Build.Revision
if there was no external thing involved here.
These external APIs change all the time, I'm not going to be there to always update the lib accordingly (and its not needed as 99% of the time those are not breaking anything either way)
But I wanna clearly communicate with the versioning which version of the API this wrapper is for, hence splitting my versioning (the first part) from the API version (second part)
The middle part is not really needed, just thought about adding that to have a proper split instead of 1.1.0-6.5.0
I just feel like seeing 1.1.0-composable-v.6.5.0
makes it clear that this is lib version 1.1.0 meant for API 6.5.0 and if the api changes to 7.0.0 I can release 1.1.0-composable-v.7.0.0
which is clearer than just having 1.1.0.128 replies