CI fails on npm ci (Node 22 matrix) due to a peer-dependency version mismatch in package.json + package-lock.json.
Surfaced during 2026-05-31 squad triage of the Operator Diagnostics lane. Blocks v1.0-prod hardening on this repo.
Observed (verify step UNKNOWN STEP):
npm error code ERESOLVE
While resolving: @eslint/js@10.0.1 / Found: eslint@9.39.4 / peer @eslint-community/eslint-utils@4.9.1 needs eslint@^6.0.0 || ^7.0.0 || >=8.0.0
Suggested fix (Codex lane — package.json + lockfile):
Either pin @eslint/js to ^9.x (matches eslint^9) OR upgrade eslint to ^10 to match @eslint/js^10.
After the fix:
- delete
node_modules + package-lock.json
npm install with npm 11+ to regenerate the lock with Linux optional deps (@emnapi/*, @rolldown/binding-*) baked in (per the existing "Lockfile" doctrine memo)- commit the regenerated
package-lock.json
- CI should go green; I'll resume the v1.0-prod harden once it does
Not blocking — Pages deploy + CNAME + tag can still ship once CI is green. No need to revert any of my squad-lane work.
CI fails on
npm ci(Node 22 matrix) due to a peer-dependency version mismatch inpackage.json+package-lock.json.Surfaced during 2026-05-31 squad triage of the Operator Diagnostics lane. Blocks v1.0-prod hardening on this repo.
Observed (verify step
UNKNOWN STEP):Suggested fix (Codex lane —
package.json+ lockfile):Either pin @eslint/js to ^9.x (matches eslint^9) OR upgrade eslint to ^10 to match @eslint/js^10.
After the fix:
node_modules+package-lock.jsonnpm installwith npm 11+ to regenerate the lock with Linux optional deps (@emnapi/*,@rolldown/binding-*) baked in (per the existing "Lockfile" doctrine memo)package-lock.jsonNot blocking — Pages deploy + CNAME + tag can still ship once CI is green. No need to revert any of my squad-lane work.