@kloczek Sorry I don't get it, they both use the same scheme:
`major.minor.micro` as the tag, and `major.minor[.micro if micro > 0]` or
however I can describe that for the asset names.
--
Reply to this email directly or view it on GitHub:
Please try to check 1.37.0 and 1.37.1.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/commit/13bc05d80f456d8ed745e4fbfbf4286a49d1acaf#commitcomment-130450748
You are receiving this because you are subscribed to this thread.
Message ID:
@kloczek not sure I get it, it's always been like that -- check e.g. the
previous release https://github.com/geany/geany/releases/tag/1.38.0: tag is
1.38.0 but tarballs use 1.38.
I guess if there's a compelling reason to do otherwise we could, but up until
now we used the full version in tags,
Assets? from https://github.com/geany/geany/releases/tag/2.0.0
Issue is that it is not possible to download dist tar ball using single version
string because all assets are on `2.0.0` tag and they
We use to name tags with the full version, including the patch level.
The rest mostly uses the short version and for API requirements it is fully
sufficient to check for major.minor as patch level versions never should
increase the API version.
What "additional assets" do you refer to?
--
Looking on https://github.com/geany/geany/releases/tag/2.0.0 looks like it is
kind of messy versioning because tag is 2.0.0 and version 2.0 and the same
version uses additional assets 樂
--
Reply to this email directly or view it on GitHub:
