From 63593434ade1c94cf233fd5783bc34a2751fb784 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=86gir=20M=C3=A1ni=20Hauksson?= <54936225+sourcehawk@users.noreply.github.com> Date: Wed, 17 Jun 2026 22:30:06 +0200 Subject: [PATCH] fix(release): use npm ci so package-lock.json is never modified in CI npm install can rewrite package-lock.json when the npm version on the runner differs from the one used locally. GoReleaser's git-dirty check then aborts the release. npm ci installs the exact locked versions without touching the file. Applies to both the frontend build target and the test-frontend target for consistency. Co-Authored-By: Claude Sonnet 4.6 --- Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index bc30305..57af556 100644 --- a/Makefile +++ b/Makefile @@ -25,7 +25,7 @@ test-go: go test -race -count=1 ./... test-frontend: - cd frontend && npm install && npm test -- --run + cd frontend && npm ci && npm test -- --run # End-to-end suite: drives the real triagent binary against scripted # claude/gh stubs. Gated behind the `e2e` build tag so it stays out of the @@ -58,7 +58,7 @@ fmt: # tracked .gitkeep so the embed still has at least one match on a fresh # `make clean` checkout. frontend: - cd frontend && npm install && npm run build + cd frontend && npm ci && npm run build rm -rf internal/web/dist mkdir -p internal/web/dist cp -a frontend/out/. internal/web/dist/