On: Maybe a better way to track the release history of a Git repo

[gouggoug]

One step further: use `git tag` for what it's for: tagging a given commit with an immutable reference (say, a version number like `v1.0.23`), and generate and publish "build artifacts" (`my-application-v1.0.23.tar.gz`, `my-application-v1.0.23` binary, `my-application-v1.0.23.tar.gz` helm chart, `my-application-v1.0.23` container image, `my-application-v1.0.23` ... whatever binary artifact)

[dgrin91 → gouggoug]

A quirk here- tags are not actually immutable in git. I agree with the premise, and use tags myself for releases, but if you rely on them being immutable then you have loaded a footgun

[gouggoug → dgrin91]

true — they only are immutable by convention and because the git command refuses by default to modify/push an existing tag.