Node 20 is no longer available in GitHub Actions

GitHub Actions runners have dropped Node 20 and now default to Node 24 for JavaScript actions. The opt‑out flag for insecure versions was removed, and self‑hosted runners on macOS 13.4‑ or earlier and ARM32 are no longer supported. Action authors must update runs.using to node24 and publish new releases.

GitHub Actions runners have removed support for Node 20 and now run JavaScript actions on Node 24. The temporary opt‑out flag that permitted insecure node versions was also withdrawn. Self‑hosted runners that operate on macOS 13.4 or earlier, as well as those on ARM32, are no longer recognized by the platform. Action developers are required to change the runs.using field to node24 and issue a new release promptly. Switching to Node 24 aligns the execution environment with the latest stable runtime, improving security and performance for workflows. The removal of the opt‑out flag eliminates a legacy workaround, encouraging all users to adopt the newer version. Incompatible self‑hosted configurations must be updated or replaced, which may affect teams that rely on older macOS builds or ARM32 hardware. It remains unclear how long GitHub will continue supporting the older runtimes on self‑hosted runners beyond the announced cutoff. The precise impact on third‑party actions that have not yet migrated to Node 24 has not been quantified. GitHub has not provided a timeline for reintroducing support for any of the discontinued environments.