ceres/VERSION.txt, branch step-re-ordering Recipe server for your favorite dishes https://cgit.xengineering.eu/ceres/atom/VERSION.txt?h=step-re-ordering 2024-11-03T16:45:07Z Add `-version` suffix to VERSION.txt 2024-11-03T16:45:07Z xengineering me@xengineering.eu 2024-11-03T16:45:07Z urn:sha1:99cff9a3102c64cd146d524524001bd6ecb246c4 This follows the process described in RELEASE.md to make sure the development versions are not mixed up with the released ones. Set version to 0.5.0 2024-11-03T15:54:04Z xengineering me@xengineering.eu 2024-11-03T15:38:09Z urn:sha1:110affc48491d3fd06296a6609abcd763fc29da0 Inject version with embed instead of build flags 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.