Add explicit process.exit() to avoid wait for hanging promises

When using the `@actions/cache` library to save cache entries, it seems that one
or more Promises remain unresolved after the save completes.
With Node20 this causes a delay when exiting the process: the default behaviour
now wait for these Promises to complete. Adding an explicit `Process.exit()`
removes the delay, returning to the Node 16 behaviour.

Fixes #1038

dist/main/index.js

@@ -140765,7 +140765,6 @@ function run() {
     });
 }
 exports.run = run;
-run();
 
 
 /***/ }),

dist/post/index.js

@@ -138076,6 +138076,7 @@ function run() {
             }
             handleFailure(error);
         }
+        process.exit();
     });
 }
 exports.run = run;
@@ -138085,7 +138086,6 @@ function handleFailure(error) {
         core.info(error.stack);
     }
 }
-run();
 
 
 /***/ }),

package-lock.json

@@ -35,7 +35,7 @@
         "eslint-plugin-prettier": "5.1.2",
         "jest": "29.7.0",
         "js-yaml": "4.1.0",
-        "npm-run-all": "^4.1.5",
+        "npm-run-all": "4.1.5",
         "patch-package": "8.0.0",
         "prettier": "3.1.1",
         "ts-jest": "29.1.1",

src/main.ts

@@ -30,5 +30,3 @@ export async function run(): Promise<void> {
         }
     }
 }
-
-run()

src/post.ts

@@ -21,6 +21,9 @@ export async function run(): Promise<void> {
 
         handleFailure(error)
     }
+
+    // Explicit process.exit() to prevent waiting for promises left hanging by `@actions/cache` on save.
+    process.exit()
 }
 
 function handleFailure(error: unknown): void {
@@ -29,5 +32,3 @@ function handleFailure(error: unknown): void {
         core.info(error.stack)
     }
 }
-
-run()