[inoway46]

Run lint-js-and-md on ubuntu-slim when the ESLint cache is restored, and fall back to ubuntu-latest otherwise. Share the lint steps through a composite action and preserve the existing lint-js-and-md required check.

Validation on the fork passed for cache misses, exact and prefix matches, and lint failure propagation.

Refs: #64972 (comment)

[nodejs-github-bot]

Review requested:

• @nodejs/actions

[inoway46]

Of 300 recent lint-js-and-md runs, 8 (2.7%) experienced a timeout, including 3 that later passed on rerun. All 8 had ESLint cache restoration failures due to HTTP 429.

Summary of the latest 300 runs:

ESLint cache	Runs (% of total)	Timeouts	Timeout rate
Restored	213 (71.0%)	0	0%
HTTP 429	58 (19.3%)	8	13.8%
Cache miss	14 (4.7%)	0	0%
Not configured	15 (5.0%)	0	0%
Total	300	8	2.7%

Fallback would switch roughly 25% of runs with ESLint caching to ubuntu-latest. Our benchmarks showed faster execution, but used public 4-CPU runners; the cost-effectiveness of private 2-CPU runners remains unverified. Given the potential cost increase and added workflow complexity, I'm closing this PR.

[MikeMcC399]

I think especially the added workflow complexity is not justified. I still believe that the runner should be updated, as you already proposed in #66409

You might consider re-opening / re-submitting #66409. It should get the chance for review from a wider range of contributors, including from @trivikr whose original #64972 issue remains unresolved.