Work around cache module modifying input paths

Bertg · WebeWizard · web-flow · commit 2bcc350a9061 · 2023-08-01T20:26:29.000+02:00
An issue in action/toolkit modifies the inputPath values passed to cache function. These changes work around this issue. For more details see: actions/toolkit#1378 Co-authored-by: Justin Leis <justin.leis@webewizard.com>
diff --git a/index.js b/index.js
@@ -31,7 +31,7 @@ const restoreCachedNpm = npmCache => {
   console.log('trying to restore cached NPM modules')
   return cache
     .restoreCache(
-      npmCache.inputPaths,
+      npmCache.inputPaths.slice(), // Copy inputPaths, to work arround bug reported in https://github.com/actions/toolkit/pull/1378
       npmCache.primaryKey,
       npmCache.restoreKeys
     )
@@ -50,7 +50,10 @@ const saveCachedNpm = npmCache => {
   console.log('saving NPM modules')
 
   return cache
-    .saveCache(npmCache.inputPaths, npmCache.primaryKey)
+    .saveCache(
+      npmCache.inputPaths.slice(), // Copy inputPaths, to work arround bug reported in https://github.com/actions/toolkit/pull/1378
+      npmCache.primaryKey
+    )
     .catch(err => {
       // don't throw an error if cache already exists, which may happen due to
       // race conditions
