v0.12.0 tag already exists

[llimeht]

There is already a v0.12.0 tag - since tags cannot be reused, that presumably means that the next version of to be released needs to be 0.12.1.

[jellybean2004]

I might have done this accidentally... It isn't linked to a release, so would it be okay to simply delete the existing tag?

[llimeht]

Other clones will only get the updated tag by jumping through hoops (such as git fetch --tags -f to force fetch the tag to move it). It's not quite as bad as rewriting history in main but it's close.

There are knock-on effects too — I noticed this just in time to not accidentally push the tag to the the debian sasdata packaging repo when I was uploading 0.12.0a1 to experimental. The 0.12.0 tag was automatically picked up by our systems (they show tags not just releases because lots of releases are hidden to the monitoring tools) The result is that we now have commits that claim to be version 0.12.0 even though they are not. I don't know if any other distro packages have done likewise. These are more minor considerations, but they do explain the context for why deleting and reusing tags is discouraged.

[jellybean2004]

I see... Thank you for pointing this out. I will bring this up in the next technical meeting to see what the best way forward is.

[krzywon]

During the technical meeting today, it was decided the next release will be v0.12.1.