Command "sfw vp install" (cwd: /home/runner/work/npmx.dev/npmx.dev) exited with code 1

Scope: all 3 workspace projects ? Verifying lockfile against supply-chain policies (2340 entries)... ✗ Lockfile failed supply-chain policy check (2340 entries in 9.5s) [ERR_PNPM_MISSING_TARBALL_INTEGRITY] 2 lockfile entries failed verification: @lunariajs/core@0.1.1 has no "integrity" field, so its downloaded tarball cannot be verified @storybook-vue/nuxt@9.0.1 has no "integrity" field, so its downloaded tarball cannot be verified The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.

The strategy configuration was canceled because "a11y.dark" failed

The operation was canceled.

Command "sfw vp install --filter . --ignore-scripts" (cwd: /home/runner/work/npmx.dev/npmx.dev) exited with code 1

? Verifying lockfile against supply-chain policies (2340 entries)... ✗ Lockfile failed supply-chain policy check (2340 entries in 8s) [ERR_PNPM_MISSING_TARBALL_INTEGRITY] 2 lockfile entries failed verification: @lunariajs/core@0.1.1 has no "integrity" field, so its downloaded tarball cannot be verified @storybook-vue/nuxt@9.0.1 has no "integrity" field, so its downloaded tarball cannot be verified The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.

Command "sfw vp install" (cwd: /home/runner/work/npmx.dev/npmx.dev) exited with code 1

Scope: all 3 workspace projects ? Verifying lockfile against supply-chain policies (2340 entries)... ✗ Lockfile failed supply-chain policy check (2340 entries in 7.5s) [ERR_PNPM_MISSING_TARBALL_INTEGRITY] 2 lockfile entries failed verification: @lunariajs/core@0.1.1 has no "integrity" field, so its downloaded tarball cannot be verified @storybook-vue/nuxt@9.0.1 has no "integrity" field, so its downloaded tarball cannot be verified The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.

Command "sfw vp install" (cwd: /home/runner/work/npmx.dev/npmx.dev) exited with code 1

Scope: all 3 workspace projects ? Verifying lockfile against supply-chain policies (2340 entries)... ✗ Lockfile failed supply-chain policy check (2340 entries in 7.9s) [ERR_PNPM_MISSING_TARBALL_INTEGRITY] 2 lockfile entries failed verification: @lunariajs/core@0.1.1 has no "integrity" field, so its downloaded tarball cannot be verified @storybook-vue/nuxt@9.0.1 has no "integrity" field, so its downloaded tarball cannot be verified The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.

Command "sfw vp install --filter . --ignore-scripts" (cwd: /home/runner/work/npmx.dev/npmx.dev) exited with code 1

? Verifying lockfile against supply-chain policies (2340 entries)... ✗ Lockfile failed supply-chain policy check (2340 entries in 7.7s) [ERR_PNPM_MISSING_TARBALL_INTEGRITY] 2 lockfile entries failed verification: @lunariajs/core@0.1.1 has no "integrity" field, so its downloaded tarball cannot be verified @storybook-vue/nuxt@9.0.1 has no "integrity" field, so its downloaded tarball cannot be verified The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.

Command "sfw vp install" (cwd: /home/runner/work/npmx.dev/npmx.dev) exited with code 1

Scope: all 3 workspace projects ? Verifying lockfile against supply-chain policies (2340 entries)... ✗ Lockfile failed supply-chain policy check (2340 entries in 7.6s) [ERR_PNPM_MISSING_TARBALL_INTEGRITY] 2 lockfile entries failed verification: @lunariajs/core@0.1.1 has no "integrity" field, so its downloaded tarball cannot be verified @storybook-vue/nuxt@9.0.1 has no "integrity" field, so its downloaded tarball cannot be verified The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.

Command "sfw vp install" (cwd: /home/runner/work/npmx.dev/npmx.dev) exited with code 1

Scope: all 3 workspace projects ? Verifying lockfile against supply-chain policies (2340 entries)... ✗ Lockfile failed supply-chain policy check (2340 entries in 7.6s) [ERR_PNPM_MISSING_TARBALL_INTEGRITY] 2 lockfile entries failed verification: @lunariajs/core@0.1.1 has no "integrity" field, so its downloaded tarball cannot be verified @storybook-vue/nuxt@9.0.1 has no "integrity" field, so its downloaded tarball cannot be verified The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.

Command "sfw vp install" (cwd: /__w/npmx.dev/npmx.dev) exited with code 1