Niklas Ye
79e77fadc6
The release skill only knew repos that deploy an image through a wrapper chart. terdut-tui publishes binaries to a Gitea release and nothing else, so its first two releases were cut by hand. It now has a .release.conf saying KIND=binary, which the skill treats as gate, tag, wait for the pipeline, then check what was published. The gate had to exist as make targets for that: fmt, lint and test, the same three the other repos have. ci.yaml and release.yaml now call them instead of carrying their own copy of gofmt, vet and the tests, so a green gate locally and a green pipeline are the same code and cannot drift. The gofmt handling moved over as written, including the comment on why both of its failure modes need catching; both fail the target, checked with a misformatted file and an unparseable one. The binaries job calls make dist too. DIST_TARGETS is now the one place that says what a release contains, and dist-assets prints the names dist builds so the skill can verify the published release against a list instead of a count. The names are unchanged, and they are the self-updater's contract with every installed binary: internal/updater matches terdut-tui-<tag>-<goos>-<goarch> exactly. CLAUDE.md gains a Release section, including that the annotated tag's message is what appears on the release page. Not run in the pipeline yet: make is in the golang image, as terdut-server's CI relies on, but this repo's workflows only exercise it on the push that carries this commit, and make dist only on the next tag. A failure in the release workflow's test job stops the publish rather than shipping something unchecked.
67 lines
2.9 KiB
Makefile
67 lines
2.9 KiB
Makefile
VERSION := $(shell git describe --tags --always --dirty)
|
|
|
|
.PHONY: build install test lint fmt dist dist-assets release-vars
|
|
|
|
build:
|
|
go build -ldflags "-X main.version=$(VERSION)" -o terdut-tui .
|
|
|
|
install:
|
|
go install -ldflags "-X main.version=$(VERSION)" .
|
|
|
|
# ci.yaml and release.yaml run `make fmt lint test`, so a green gate here and a green
|
|
# pipeline are the same code rather than two descriptions of it. It is also what the
|
|
# release skill runs before tagging.
|
|
|
|
# Covers the API client against a stub server, the sign-in flow, the Update state
|
|
# machine, and View rendering -- all pure enough to test without a terminal.
|
|
test: ## Run the test suite
|
|
go test ./...
|
|
|
|
lint: ## go vet
|
|
go vet ./...
|
|
|
|
# This exists because `go vet` does not look at import order: the move to
|
|
# git.ryuvia.com rewrote every import path without re-sorting, the new path sorts
|
|
# before github.com/..., and both repos sat unformatted through a green CI run and
|
|
# a release before anyone noticed.
|
|
#
|
|
# Both of gofmt's failure modes need handling, and they are not alike. A file that
|
|
# is merely misformatted is listed on stdout with exit 0 -- so the failure has to
|
|
# be raised by hand. A file that does not parse is the opposite: nothing on stdout
|
|
# and exit 2, which a naive `[ -n "$$unformatted" ]` reads as success. The first
|
|
# draft of this target had exactly that hole.
|
|
fmt: ## Fail on files that are not gofmt'd
|
|
@if ! unformatted=$$(gofmt -l .); then \
|
|
echo "gofmt could not parse the tree:"; gofmt -l .; exit 1; \
|
|
fi; \
|
|
if [ -n "$$unformatted" ]; then \
|
|
echo "not gofmt'd:"; echo "$$unformatted"; gofmt -d .; exit 1; \
|
|
fi
|
|
|
|
# What a release publishes. The asset names matter beyond being tidy: internal/updater
|
|
# looks for exactly terdut-tui-<tag>-<goos>-<goarch> in the latest release and reports
|
|
# every available name when it cannot find one. Renaming the pattern here breaks
|
|
# self-update for every installed binary.
|
|
DIST_TARGETS := linux/amd64 linux/arm64 darwin/amd64 darwin/arm64
|
|
|
|
dist: ## Build every release binary into dist/ (VERSION=vX.Y.Z to name them)
|
|
@set -eu; mkdir -p dist; \
|
|
for target in $(DIST_TARGETS); do \
|
|
goos="$${target%/*}"; goarch="$${target#*/}"; \
|
|
out="dist/terdut-tui-$(VERSION)-$$goos-$$goarch"; \
|
|
echo "building $$out"; \
|
|
GOOS="$$goos" GOARCH="$$goarch" go build -ldflags "-X main.version=$(VERSION)" -o "$$out" .; \
|
|
done
|
|
|
|
# The names dist produces, one per line, so the release skill can check the published
|
|
# release has every one of them rather than a count.
|
|
dist-assets: ## Print the asset names a release of VERSION carries
|
|
@for target in $(DIST_TARGETS); do \
|
|
echo "terdut-tui-$(VERSION)-$${target%/*}-$${target#*/}"; \
|
|
done
|
|
|
|
# Read by the release skill for a repo that publishes binaries and no image or chart
|
|
# (KIND=binary in .release.conf). There is nothing to say about images or charts.
|
|
release-vars: ## Print the variables the release process reads
|
|
@printf 'APP=terdut-tui\n'
|