fix: use more unique working directory

RUNNER_TEMP will predictably become a more common place for workflow users to put stuff on, given that the upcoming examples will make use of it. Therefore, it's important to use a reproducible but unpredictable path to avoid messing with data that other steps rely on. Neither Node nor JavaScript have good features for generating random constants at build time or managing the built-in PRNG seed, so let's sidestep potential problems by hardcoding a random 128 bit hex string that I have just generated, and should be pretty unique.
ComunidadAylas · Jun 14, 2023 · 84dd694 · 84dd694
1 parent d2462c1
commit 84dd694
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/dist/cleanup_working_directory/index.js b/dist/cleanup_working_directory/index.js
diff --git a/dist/main/index.js b/dist/main/index.js
diff --git a/src/working_directory.ts b/src/working_directory.ts
@@ -16,7 +16,7 @@ class WorkingDirectory {
     binaryExtension: string;
 
     constructor() {
-        this.path = path.join(getEnvOrThrow('RUNNER_TEMP'), 'packsquash');
+        this.path = path.join(getEnvOrThrow('RUNNER_TEMP'), 'packsquash-1040c4a92c59083e9c206174a4ad7103');
         this.binaryExtension = getEnvOrThrow('RUNNER_OS') == 'Windows' ? '.exe' : '';
     }