News for hackers. Stuff that matters.
Re:Maybe a better way to track the release history of a Git ... by lijok on Tuesday October 13, 2026 @05:52PM (#50079397)
Or commit a file to main that represents a release and build your automations off that
Re:Maybe a better way to track the release history of a Git ... by gouggoug on Tuesday October 13, 2026 @07:04PM (#50080193)
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)
Re:Maybe a better way to track the release history of a Git ... by dgrin91 on Tuesday October 13, 2026 @08:52PM (#50081047)
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
Re:Maybe a better way to track the release history of a Git ... by gouggoug on Tuesday October 13, 2026 @09:03PM (#50081109)
true — they only are immutable by convention and because the git command refuses by default to modify/push an existing tag.