Scaffold workflows should opt into Node.js 24 actions (June 2026 deadline)

[genesis-dev-bot]

What went wrong

All genesis-scaffolded workflow files use actions/checkout@v4 and oven-sh/setup-bun, which run on Node.js 20. GitHub Actions will force Node.js 24 as default starting June 2, 2026 (deprecation warnings already appearing in all workflow runs). Every project scaffolded by genesis today will silently accumulate these warnings and then break at the deadline without intervention.

Which project hit it

ronny-learns-ai — evolver noticed the deprecation warnings in all workflow logs as of 2026-04-10. Fixed in that project by adding FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true as a workflow-level env: block to all 5 workflows (commit aae790a).

Proposed fix

In the genesis workflow templates (wherever genesis-orchestrator.yml, genesis-evolver.yml, genesis-events.yml, genesis-push-trigger.yml are scaffolded), add:

env:
  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true

at the workflow level (outside jobs:), after permissions:.

This opts all new projects into Node.js 24 immediately, eliminating deprecation noise and making the June 2 forced rollover a no-op.

Timeline

• June 2, 2026: Node.js 24 becomes the default (actions running on Node.js 20 may behave unexpectedly)
• September 16, 2026: Node.js 20 removed from runners entirely
• Today (2026-04-10): ~7.5 weeks until the first deadline

/label needs:evolver