Proper version tag when releasing

Question

0x0L opened this issue 2 years ago · 3 comments

The artifacts are produced with a 0.1 version number (see assets in Release too)

Also I'd need to force a proper rebuild after adding a tag

Answer 1 · 2023-03-13T09:22:21.000Z

This is "intended" in the way setuptools_scm works. What about sticking to semantic versioning, and considering all versions <=1.0 unstable?

So tagging 0.1 instead of 0.1a. https://semver.org/#spec-item-4

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

This will make automatic versioning correct.

Answer 2 · 2023-03-13T12:06:08.000Z

What is intended ? The current tag is 0.3b on my local machine, not on the CI

Answer 3 · 2023-03-13T18:36:21.000Z

Yeah, sorry. I thought setuptools_scm was not able to parse the tag we were producing. This #31 should fix it.