From ec87844e545e3896633e1eb972735f523149dda3 Mon Sep 17 00:00:00 2001 From: petergstfsn <171875562+petergstfsn@users.noreply.github.com> Date: Mon, 24 Aug 2026 23:16:30 +0000 Subject: [PATCH] ci: use npm ci now that package-lock.json is tracked The web job carried a comment claiming package-lock.json is intentionally untracked, so npm ci is not usable. The lockfile is tracked at the repo root and is not gitignored, so that comment is stale and npm install was doing an unpinned resolve on every run. Switch to npm ci for reproducible installs, matching the verify and upload jobs in cloudflare.yml, and drop the stale comment. Co-Authored-By: Claude Claude-Session: https://claude.ai/code/session_01HdERD2o3Kmd5RmFXS7s4xW --- .github/workflows/ci.yml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index d8c2da3..a8ca0f0 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -14,8 +14,7 @@ jobs: - uses: actions/setup-node@v4 with: node-version: 22 - # package-lock.json is intentionally untracked, so npm ci is not usable. - - run: npm install + - run: npm ci - run: npx tsc -b working-directory: apps/web - run: npm run test:web