Always create annotated tags for releases

[sdruskat]

The recent releases 0.8.1b1 and 0.8.1 have been tagged with lightweight tags only.

In Software Heritage, only annotated tags are picked up as "releases" and hence get listed as such. In our case, the archive lists exactly one release, proof-of-concept, as this is an annotated tag, which, however, isn't listed as a release on GitHub with its own release page.

Using lightweight tags for releases therefore leads to a discrepancy between the information in the source code repo, that on Zenodo, and that on SWH.

To avoid disconnects between these three platforms, we should use annotated tags for all releases to make sure they're being harvested as such on SWH.

[led02]

Thanks for the hint, wasn't aware of that.

Is it possible to annotate tags later or do we need to tag again?

Is this already reflected in our release process?

[sdruskat]

Is it possible to annotate tags later or do we need to tag again?

With newer versions of git I think you'll have to force tag over an existing tag. I'm not sure: a) what this would do for the GitHub release, b) what this would do for the Zenodo publication. Could be checked in a test repo? (I have no time to do this though.)

Is this already reflected in our release process?

Not yet. Should I draft this up?

[zyzzyxdonta]

We could adopt signed tags for releases. Signed tags are always annotated.