[heft-lint-plugin] Stabilize linter cache filename using tsconfig path hash

[Copilot]

Summary

The linter cache filename used a hash of all input filenames, causing cache churn when files were added/removed. This stabilizes the cache filename by hashing the tsconfig path instead, while moving the files hash into the cache data for validation.

Fixes #5436

Details

Cache filename generation (LinterBase.ts):

• Hash suffix now derived from project-relative tsconfig path extracted from program.getCompilerOptions().configFilePath
• Files hash moved to ILinterCacheData.filesHash field for cache validation
• File paths are sorted before hashing to ensure stable hash values
• Uses base64url encoding for hashes (filesHash without truncation, hashSuffix truncated to 8 chars for filename)
• Cache invalidated if either cacheVersion or filesHash changes

Simplified implementation (LintPlugin.ts):

• No manual tsconfig path tracking needed - extracted directly from TypeScript program
• Cleaner code without additional tuple elements or parameter forwarding

Before:

// Cache filename: _eslint-xj9kL2mP.json (hash of all file paths)
// Changes when files added/removed

After:

// Cache filename: _eslint-a7B3cD4e.json (hash of "tsconfig.json" path)
// Stable across file changes, invalidated via filesHash in cache data

How it was tested

• ✅ All existing unit tests pass (8 tests)
• ✅ Build succeeds without errors
• ✅ CodeQL security scan shows no vulnerabilities
• Manual verification that cache filename is now stable based on tsconfig path

Impacted documentation

None - this is an internal implementation change that does not affect the public API or user-facing behavior.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[heft-lint-plugin] Stabilize the hash suffix in the linter cache file</issue_title>
<issue_description>

rushstack/heft-plugins/heft-lint-plugin/src/LinterBase.ts

Lines 86 to 95 in 3f7b8f9

	const relativePaths: Map<string, string> = new Map();
	const fileHash: Hash = createHash('md5');
	for (const file of options.typeScriptFilenames) {
	// Need to use relative paths to ensure portability.
	const relative: string = Path.convertToSlashes(path.relative(commonDirectory, file));
	relativePaths.set(file, relative);
	fileHash.update(relative);
	}
	const hashSuffix: string = fileHash.digest('base64').replace(/\+/g, '-').replace(/\//g, '_').slice(0, 8);

Update the hash calculation for the linter cache filename to only be a hash of the project-relative path of the tsconfig file that corresponds to the program instance, rather than a hash of the list of file names.

The hash of the list of filenames may be placed inside of the cache file instead as a check to verify that it was run with the same files.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [heft-lint-plugin] Stabilize the hash suffix in the linter cache file #5436

---

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

[dmichon-msft]

Get the config file path from the program's getCompilerOptions().configFilePath (may require null checking). This will greatly simplify the code change.

[dmichon-msft]

@copilot address feedback

[Copilot]

Get the config file path from the program's getCompilerOptions().configFilePath (may require null checking). This will greatly simplify the code change.

Done in commit ba0baea. The implementation now uses program.getCompilerOptions().configFilePath as suggested, which greatly simplified the code.

[dmichon-msft]

@copilot Run rush change --no-fetch --bulk --bump-type patch --message "${description of changes}" to create the necessary change file.

[Copilot]

@copilot Run rush change --no-fetch --bulk --bump-type patch --message "${description of changes}" to create the necessary change file.

Done in commit 40868de. Created the change file for @rushstack/heft-lint-plugin with bump type patch.