You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix Node.js 22 V8 cache crash by reverting to Node 20
The previous attempt to disable yarn caching for Node 22 using cache: '' caused CI failures because GitHub Actions setup-node doesn't accept empty strings for the cache parameter and still attempts to initialize caching, resulting in "Could not get yarn cache folder path" errors.
This commit reverts all workflows to use Node 20 until the V8 bug is resolved. This is a temporary workaround that ensures CI stability.
Changes:
- Revert lint-js-and-ruby.yml from Node 22 to Node 20 with normal caching
- Revert main.yml matrix to use Node 20 for both latest and minimum dependency levels
- Simplify package-js-tests.yml to only test Node 20
- Remove conditional cache logic that was causing failures
- Remove conditional frozen-lockfile flag that depended on Node 22
Related: nodejs/node#56010
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
0 commit comments