Recipe server for your favorite dishes https://cgit.xengineering.eu/ceres/atom/version.go?h=step-re-ordering 2024-11-03T15:54:04Z 2024-11-03T15:54:04Z xengineering me@xengineering.eu 2024-11-03T15:53:31Z urn:sha1:6c8ac2b906d8d42d3765c4821ebbafc72c43663b This contained an unwanted newline. 2024-10-23T16:02:06Z xengineering me@xengineering.eu 2024-10-23T16:02:06Z urn:sha1:98d6bc5dda57146cdf26de4adc5b2cf747d81934 2024-10-23T14:04:22Z xengineering me@xengineering.eu 2024-10-23T14:01:36Z urn:sha1:2195cfce131ee599c71d0c426a7eea70ed52345f The build flags made the basic build and debug calls quite complex and bound this strictly to Git repositories which is a problem if the source code is passed around as tar archive. Embedding this via Go's embed package and a VERSION.txt file makes this way easier. A simple `go build` command is sufficient to build ceres. To make sure the version string is extended by a `-devel` marker and that this marker is removed before a release a RELEASE.md file was added as a checklist for releases. 2024-05-08T18:59:41Z xengineering me@xengineering.eu 2024-05-08T18:59:41Z urn:sha1:5a09313066f5594ca9e3917c00821e443dcba7bc This variable will be the only used representation for version information. It can trivially be used for an equality check. Further data as semantic versioning must be parsed from this string. 2024-05-01T12:52:21Z xengineering me@xengineering.eu 2024-05-01T12:50:33Z urn:sha1:07f011bbbb22de9e7b4fd4af30fa0a92ee25b6d8 This ensures that Ceres is never executed without Git version information. This removes the requirement to check for this on every use. To ensure the server does not work with an incompatible storage directory it is in every case needed to know the exact version of the running executable. 2024-04-30T18:50:31Z xengineering me@xengineering.eu 2024-04-30T18:50:31Z urn:sha1:581feffe944a5eeb42f4cba3e4d24f0e1d5b0b3f The output of `git describe --dirty --always` is passed as a string via Go build flags.