[Question] Use annotated tags for future releases about kitodo-presentation

[sebastian-meyer]

What's the benefit of annotated tags over lightweight tags?

Tags are currently set when preparing a new release. This is automated by GitHub as part of the release workflow and I don't see how I could GitHub tell to use another kind of tag...

[stweil]

Annotated tags are handled similar to commits, for example using the command line:

# Create an unsigned annotated tag.
git tag -a -m "New release v6.0.1" v6.0.1
git push origin v6.0.1

# Create a signed annotated tag.
git tag -s -m "New release v6.0.2" v6.0.2
git push origin v6.0.2

Those steps are done before the release is published on GitHub, so the GitHub release process won't create an additional tag.

Like a commit an annotated tag has an author, a timestamp, a message and optionally a digital signature. I suggest to use signed annotated tags, but even unsigned annotated tags are an improvement compared with lightweight tags.

As I wrote in my report above, git recommends using annotated tags for releases.
The command git describe looks for annotated tags by default.

This is the answer to your question from a chatbot:

• Annotated tags allow you to add a message to the tag, which provides more information about why the tag was created
  and what changes were made in the codebase. This can be useful for documenting changes and providing context for other
  developers.
• Annotated tags also allow you to sign your commits, which can help ensure that your code has not been tampered with
  and is authentic.
• Annotated tags provide a more comprehensive commit history, making it easier to understand how different versions of
  your code are related and how they have changed over time.
• Lightweight tags do not have these additional features, so if you need more advanced version control functionality,
  annotated tags may be a better choice.