container-release-action-0.0.0
checks.x86_64-linux.action
· build #51
· raw
unpackPhase
1unpacking source archive /nix/store/nv7j71ad0hf0in73s85zhfn5xb2sgrpn-source2source root is sourcepatchPhase
3Executing npmConfigHook4Configuring npm5Validating consistency between /build/source/package-lock.json and /nix/store/fw5ba40bbwbhnnngq14jgldrk3a93sw3-container-release-action-0.0.0-npm-deps/package-lock.json617c177< "@types/node": "26.4.0",8---9> "@types/node": "26.2.0",10785,787c785,78711< "version": "26.4.0",12< "resolved": "https://registry.npmjs.org/@types/node/-/node-26.4.0.tgz",13< "integrity": "sha512-faiGnoIrLH/V8cibOMEAZ8pMw6oXqSukl29ra4mN8GdaB2ZewzeaLj+INpV5N+Z1eKWzY+IzaIZH2EIR6YZRNQ==",14---15> "version": "26.2.0",16> "resolved": "https://registry.npmjs.org/@types/node/-/node-26.2.0.tgz",17> "integrity": "sha512-5IviulTZeRNp2vAJ514cc/HUlY5nZ9fCbq9DMyC52BrhFZACo3nI0R7qBxhQmo/d27NFe96ur/b7Wwxklda+kg==",1819ERROR: npmDepsHash is out of date2021The package-lock.json in src is not the same as the in /nix/store/fw5ba40bbwbhnnngq14jgldrk3a93sw3-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