Closed cacack closed 1 year ago
Ultimately I may not care as I'm using tr
in other make recipes to adjust the semantic version to the package specific version. I haven't gotten to the point of consuming the APK from our repo to know if apk
itself cares; I suspect it may throw off it's version graph but we rarely produce pre-release versions internally so 🤷 .
can you check #725
thanks for the issue btw :D
What happened?
Using env variables to set the package version with a pre-release specifier,
nfpm
doesn't create a valid version specifier for Alpine packages as documented here: https://wiki.alpinelinux.org/wiki/Package_policies.I'd expect the package version to be
1.6.0_rc
but instead it is1.6.0rc
How can we reproduce this?
nfpm version
Search
Code of Conduct
Additional context
Version is being computed using
svu
.Thanks for providing two awesome tools!