Problem

The cache-save.ts file was calling process.exit(0) when used as a post-action step in GitHub Actions workflows, which could terminate the entire workflow prematurely. This happened because:

1. The run() function had an earlyExit parameter that would call process.exit(0) when true
2. The file automatically executed run(true) at module load time
3. Since this file is used as the post action step in action.yml, it would exit the process immediately after caching

Root Cause

// Problematic code
export async function run(earlyExit?: boolean) {
  // ... cache logic ...
  if (earlyExit) {
    process.exit(0);  // ❌ Terminates the entire workflow
  }
}

run(true);  // ❌ Always calls with early exit enabled

This pattern was apparently added to "resolve issue with slow post action step" according to the comment, but using process.exit(0) in a GitHub Actions post-step is incorrect and can cause unexpected workflow termination.

Solution

Removed the earlyExit parameter and process.exit(0) call entirely, following the same pattern used in setup-node.ts:

// Fixed code
export async function run() {
  // ... cache logic (unchanged) ...
  // No more process.exit(0)
}

run();  // ✅ Normal execution without forced exit

Testing

• All existing tests pass (213/213) ✅
• Tests already expected run() to be called without parameters
• Build and linting work correctly
• No breaking changes to the caching functionality

This fix ensures that the cache-save post-action step completes normally without prematurely terminating the GitHub Actions workflow, while maintaining all existing caching functionality.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.