req: complete relation between version tag and release asset filenames

[bo0tzz]

The release assets have a +build_num in their filenames, while this number isn't in any machine-readable field on the release, making it very challenging to automate dependency updates. Could you either include the build number in the version (like the 1.0 tags did), or drop it from the filename?

[pszymich]

Hello @bo0tzz, the build metadata conforms to the semantic versioning spec: https://semver.org/#spec-item-10
As stated in the specification, the build metadata does not contribute to the version precedence.

[bo0tzz]

This request isn't about version precedence, it's about being able to construct the asset filenames from the version