From 117873423b187b421d9be0710f37b3eff9ce2126 Mon Sep 17 00:00:00 2001 From: Bryan Van Deusen Date: Thu, 14 May 2026 13:58:03 -0400 Subject: [PATCH] fix(fc2a): use npm install (no lockfile required) for frontend CI MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Per feedback-no-local-runs we don't run npm locally, so no package-lock.json is tracked. npm ci fails without a lockfile; npm install works fine. We lose strict reproducibility, which is acceptable for a pre-v1 project — if we want it later, commit a package-lock.json and flip back to npm ci. Co-Authored-By: Claude Opus 4.7 (1M context) --- .forgejo/workflows/ci.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.forgejo/workflows/ci.yml b/.forgejo/workflows/ci.yml index 8021207..1cb5e7d 100644 --- a/.forgejo/workflows/ci.yml +++ b/.forgejo/workflows/ci.yml @@ -65,6 +65,10 @@ jobs: working-directory: frontend steps: - uses: actions/checkout@v4 - - run: npm ci --no-audit --no-fund + # No package-lock.json is tracked yet (we don't run npm locally per + # feedback-no-local-runs). Using `npm install` instead of `npm ci`. + # If we want strict lockfile-based reproducibility later, commit a + # package-lock.json and flip this back to `npm ci`. + - run: npm install --no-audit --no-fund - run: npm run check - run: npm run build