Lockfile is up to date, resolution step is skipped
Progress: resolved 1, reused 0, downloaded 0, added 0
Packages: +15
+++++++++++++++
 ERR_PNPM_TARBALL_INTEGRITY  Got unexpected checksum for "/home/user/builds/zync-invariantum-recovery-5fc7450fae1c/.invariantum/runner/packages/invariantum-cli-0.1.0.tgz". Wanted "sha512-LEsK62xceIPQCAipkoX0q+NnKhiyHA2N0ic0O4KEfILQagxKA3/eQNmQSLvFobQXfHeQDmRQS3oRQYvus2zazA==". Got "sha512-37p0VpxUFRMLGDNYhqwhmod5e9O+NU8xGBH/Jc+Y1zalSIrKRH52aVKz4G8QJclXNBugBAKT23glkyH5jAwh7w==".

This error may happen when a package is republished to the registry with the same version.
In this case, the metadata in the local pnpm cache will contain the old integrity checksum.

If you think that this is the case, then run "pnpm store prune" and rerun the command that failed.
"pnpm store prune" will remove your local metadata cache.
e2e-remote: client exit=1 (no server; debian1)
command-supervisor classification=opaque-exit
command-supervisor last-event=none
command-supervisor process-tree=empty