Hi,
Our release policy requires that we vote on release candidates leading up to a release.
With python, we use "(\d+).(\d+).(\d+).dev(\d+)" format to represent release candidates leading up to a release (so that we can leverage the PyPI prerelease functionality), i.e.:
2.1.0.dev0 is first release candidate.2.1.0.dev1 or additional release candidates may occur if the first one didn't pass muster in the vote.2.1.0 is the ultimate release tag.
Under this policy, we will always have 2 tags on the same commit, normally 2.1.0.dev0 and 2.1.0 will appear on the same commit.
Naturally, we want the release tag to be chosen in priority over the release candidate tag, but the behavior appears to be unstable:
- On my laptop, it appears to chose
2.1.0 with both tags present
- In github CI, where the release assets (source distribution and wheels) are generated,
2.1.0.dev0 is selected even when the 2.1.0 tag is present.
Is this a bug ? Or is there some configuration in versioneer I need to specify the tag prioritization ?
Hi,
Our release policy requires that we vote on release candidates leading up to a release.
With python, we use
"(\d+).(\d+).(\d+).dev(\d+)"format to represent release candidates leading up to a release (so that we can leverage the PyPI prerelease functionality), i.e.:2.1.0.dev0is first release candidate.2.1.0.dev1or additional release candidates may occur if the first one didn't pass muster in the vote.2.1.0is the ultimate release tag.Under this policy, we will always have 2 tags on the same commit, normally
2.1.0.dev0and2.1.0will appear on the same commit.Naturally, we want the release tag to be chosen in priority over the release candidate tag, but the behavior appears to be unstable:
2.1.0with both tags present2.1.0.dev0is selected even when the2.1.0tag is present.Is this a bug ? Or is there some configuration in versioneer I need to specify the tag prioritization ?