Summary: Our GitHub Actions workflows are using deprecated Node.js 20, which will be removed from runners on September 16th, 2026.
Why We Need to Upgrade
Deprecation Timeline
Current State: Actions running on Node.js 20 (deprecated)
June 2nd, 2026: Node.js 24 becomes the default runtime
September 16th, 2026: Node.js 20 will be removed entirely from GitHub Actions runners
Impact if Not Upgraded
❌ Workflow failures starting June 2nd, 2026 (if actions don't support Node.js 24)
❌ Complete breakage after September 16th, 2026 (Node.js 20 removed)
❌ Security vulnerabilities from running unsupported Node.js versions
❌ Maintenance burden from using outdated dependencies
Benefits of Upgrading
✅ Future-proof workflows against runner changes
✅ Security improvements from latest Node.js LTS
✅ Performance gains from Node.js 24 optimizations
✅ Continued support from action maintainers
Required Action: Update to latest version supporting Node.js 24.
Summary: Our GitHub Actions workflows are using deprecated Node.js 20, which will be removed from runners on September 16th, 2026.
Why We Need to Upgrade
Deprecation Timeline
Current State: Actions running on Node.js 20 (deprecated)
June 2nd, 2026: Node.js 24 becomes the default runtime
September 16th, 2026: Node.js 20 will be removed entirely from GitHub Actions runners
Impact if Not Upgraded
❌ Workflow failures starting June 2nd, 2026 (if actions don't support Node.js 24)
❌ Complete breakage after September 16th, 2026 (Node.js 20 removed)
❌ Security vulnerabilities from running unsupported Node.js versions
❌ Maintenance burden from using outdated dependencies
Benefits of Upgrading
✅ Future-proof workflows against runner changes
✅ Security improvements from latest Node.js LTS
✅ Performance gains from Node.js 24 optimizations
✅ Continued support from action maintainers
Required Action: Update to latest version supporting Node.js 24.