Trying to active PNPM with an SHA to work around package signature issue

Lombiq · Feb 2, 2025 · f8d3c0a · f8d3c0a
1 parent 2bae819
commit f8d3c0a
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/Lombiq.NodeJs.Extensions/build/NodeJsExtensionsNpmPackage.targets b/Lombiq.NodeJs.Extensions/build/NodeJsExtensionsNpmPackage.targets
@@ -7,7 +7,7 @@
     <!-- Retry to work around sporadic errors when this is run by multiple threads at the same time. -->
     <MSBuild
       Projects="$(RetryCommand)"
-      Properties="Command=npm install --global corepack@latest &amp;&amp; corepack enable &amp;&amp; corepack prepare [email protected] --activate &amp;&amp; echo PNPM activated via corepack;NxVerbosity=$(NxVerbosity);WorkingDirectory=$(WorkingDirectory)" />
+      Properties="Command=corepack enable &amp;&amp; corepack prepare [email protected]+sha1.aa4bc353b5f59fe1f1df5d802ce049ddf7f3c60e --activate &amp;&amp; echo PNPM activated via corepack;NxVerbosity=$(NxVerbosity);WorkingDirectory=$(WorkingDirectory)" />
   </Target>
 
   <!-- Adding Node.js Extensions as an npm package to the consuming project in order to be able to run the build, clean,