Skip to content

#1 Persistent memory for AI coding agents based on real-world benchmarks

ci: two-step install so npm ci has a lockfile on this branch

Rohit Ghumarefab246a3fd2a
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index ab430f5a..42b14b9b 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -17,6 +17,10 @@ jobs:
- uses: actions/setup-node@v4
with:
node-version: ${{ matrix.node-version }}
- - run: npm ci --legacy-peer-deps
+ # Two-step install: generate a lockfile in-runner with
+ # --package-lock-only, then install from it with `npm ci`.
+ # Lockfiles are gitignored at the repo level.
+ - run: npm install --package-lock-only --legacy-peer-deps --no-audit --no-fund
+ - run: npm ci --legacy-peer-deps --no-audit --no-fund
- run: npm run build
- run: npm test
diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml
index 6f3e9582..aadd922e 100644
--- a/.github/workflows/publish.yml
+++ b/.github/workflows/publish.yml
@@ -25,7 +25,13 @@ jobs:
node-version: 22
registry-url: https://registry.npmjs.org
- - run: npm ci --legacy-peer-deps
+ # Two-step install: generate a lockfile in-runner with
+ # --package-lock-only, then install from it with `npm ci`. Gives a
+ # single deterministic dep graph across build / test / publish
+ # within one job — important because publish uses `--provenance`.
+ # Lockfiles are gitignored at the repo level.
+ - run: npm install --package-lock-only --legacy-peer-deps --no-audit --no-fund
+ - run: npm ci --legacy-peer-deps --no-audit --no-fund
- run: npm run build
- run: npm test