Skip to content

Commit 1b7aceb

Browse files
committed
fix: ensure correct version is set on binaries
Previous bins report the incorrect version: (eg after downloading 0.2.0 the binary tells me it is `v0.1.2-13-gc533a0e`). I am not sure why this happens, perhaps the action cannot see the new tag? This doesn't make much sense as it is a new tag which triggers the release. idk. After messing around with another binary, I think this should save the correct thing.
1 parent bead002 commit 1b7aceb

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

Makefile

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# Build Information
22
BUILD_DATE := $(shell date +%Y-%m-%dT%H:%M:%SZ)
33
GIT_COMMIT := $(shell git rev-parse --short HEAD)
4-
VERSION := $(shell git describe --always --match "v*")
4+
VERSION := $(shell git describe --tags --abbrev=0)
55
VERSION_PKG := github.com/weaveworks-liquidmetal/flintlock/internal/version
66
OS := $(shell go env GOOS)
77
ARCH := $(shell go env GOARCH)

0 commit comments

Comments
 (0)