Stuart Henderson writes:
> On 2021/04/13 14:02, Daniel Jakots wrote: >> This is using a random commit from upstream, isn't it? Would it be >> possible to use a release/tag instead? > > ahahahahaa > > You're not familiar with the ways of the go stuff are you ;) A bit more info on this. Since minio doesn't follow semver Go makes a "semver like" version (similar to what we do for all the GH_COMMIT stuff!). Typically when this is the case, I try to align the commit with the "nearest" version: https://github.com/openbsd/ports/blob/master/net/miniflux/Makefile#L9 So in the above, 2.0.28 is the version upstream intended and the date component is the date the commit was made (taken from the MODGO_VERSION line). The best thing (for all the consumers of minio stuff) is for them to follow semver.. but : https://github.com/minio/minio/issues/2318#issuecomment-235992350