container-release-action-0.0.0
checks.x86_64-linux.action
· build #39
· raw
unpackPhase
1unpacking source archive /nix/store/4p5m5q9m3x234ska0gdzkspd5wiv9j1y-source2source root is sourcepatchPhase
3Executing npmConfigHook4Configuring npm5Validating consistency between /build/source/package-lock.json and /nix/store/8f1kr8n5jbm8grj34d9gr6rvnyj6nvjv-container-release-action-0.0.0-npm-deps/package-lock.json619c197< "eslint": "10.9.0",8---9> "eslint": "10.8.1",101327,1329c1327,132911< "version": "10.9.0",12< "resolved": "https://registry.npmjs.org/eslint/-/eslint-10.9.0.tgz",13< "integrity": "sha512-5KeEOJZBfEVA47boFiBsf+6MmmJpffM7qEBg4pLla2e4nlKgdKlqCW0oSLOGsT8Wl5uCGJptLV1bkaiShj90Gw==",14---15> "version": "10.8.1",16> "resolved": "https://registry.npmjs.org/eslint/-/eslint-10.8.1.tgz",17> "integrity": "sha512-wqA7W2jbsC/BnV9Iv1UZpKVFkO1AdNoSmYW8NWG4HNOBbkAMvIqDZ27pI2f07dqn583NcIC44ckjAcOXDL1QbQ==",1819ERROR: npmDepsHash is out of date2021The package-lock.json in src is not the same as the in /nix/store/8f1kr8n5jbm8grj34d9gr6rvnyj6nvjv-container-release-action-0.0.0-npm-deps.2223To fix the issue:241. Use `lib.fakeHash` as the npmDepsHash value252. Build the derivation and wait for it to fail with a hash mismatch263. Copy the 'got: sha256-' value back into the npmDepsHash field27