fix(deploy): use bun --frozen-lockfile instead of npm install

npm install with no committed package-lock.json re-resolved semver
ranges fresh on every deploy instead of pinning to bun.lock (the
project's actual lockfile) — a supply-chain integrity gap flagged by
automated commit review. Use bun, the frontend's real package manager,
with --frozen-lockfile so deploys are reproducible.

Claude-Session: https://claude.ai/code/session_01F1M1Jic1wTSn4igUENynmZ
This commit is contained in:
loki5512344 2026-09-28 15:30:42 +02:00
parent 4c2486d7cd
commit 1998cdae24
Signed by: boba
GPG key ID: 253067914055423B

View file

@ -14,8 +14,8 @@ docker compose -f docker-compose.prod.yml up -d --build
echo "==> Building frontend"
cd "$REPO_DIR/frontend"
npm install
npm run build
bun install --frozen-lockfile
bun run build
echo "==> Syncing frontend build to $FRONTEND_ROOT"
mkdir -p "$FRONTEND_ROOT"