release: v1.8.0

I know it's generally frowned upon to make edits to existing migrations,
but this should be a transparent change that makes absolutely no
difference to existing users with the migration already applied.
However, PostgreSQL 9.6 users (still the default on Debian Stretch)
stand to gain a lot from this simple change.

.gitlab-ci.yml

@@ -36,7 +36,7 @@ go-test:
   stage: go-test
   image: golang:1.14
   services:
-    - postgres:latest
+    - postgres:9.6
   variables:
     POSTGRES_USER: postgres
     POSTGRES_PASSWORD: postgres

api/Makefile

@@ -26,11 +26,11 @@ clean:
 
 devel-go:
 	GO111MODULE=on go mod vendor
-	GO111MODULE=on go build -mod=vendor -v -o $(GO_DEVEL_BUILD_BINARY) -ldflags "-X main.version=$(shell git describe --tags)"
+	GO111MODULE=on go build -mod=vendor -v -o $(GO_DEVEL_BUILD_BINARY) -ldflags "-X main.version=v1.8.0"
 
 prod-go:
 	GO111MODULE=on go mod vendor
-	GO111MODULE=on go build -mod=vendor -v -o $(GO_PROD_BUILD_BINARY) -ldflags "-X main.version=$(shell git describe --tags)"
+	GO111MODULE=on go build -mod=vendor -v -o $(GO_PROD_BUILD_BINARY) -ldflags "-X main.version=v1.8.0"
 
 test-go:
 	GO111MODULE=on go mod vendor

db/20190913175445-delete-comments.sql

@@ -1,6 +1,6 @@
 DROP TRIGGER IF EXISTS commentsDeleteTrigger ON comments;
 
-DROP FUNCTION IF EXISTS commentsDeleteTriggerFunction;
+DROP FUNCTION IF EXISTS commentsDeleteTriggerFunction();
 
 ALTER TABLE comments
   ADD deleted BOOLEAN NOT NULL DEFAULT false;