Update GitHub Actions for Node.js 24 compatibility #155

Closed
opened 2026-04-05 16:22:22 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @pheus on 3/12/2026

Proposed Changes

Review and update the GitHub Actions in workflows on main that are still running on deprecated Node.js 20, and bump them to versions that support Node.js 24 where available.

The warning currently mentions:

  • actions/checkout@v4
  • actions/setup-node@v4
  • actions/setup-python@v5
  • astral-sh/ruff-action@4919ec5cf1f49eff0871dbcea0da843445b837e6

While looking through the workflows on main, there are a few additional actions that should be included in scope as well:

  • actions/create-github-app-token@v1
  • EndBug/add-and-commit@a94899bca583c204427a224a7af87c02f9b325d5
  • actions/stale@v9 (used in both close-incomplete-issues.yml and close-stale-issues.yml)

Affected workflows currently include:

  • ci.yml
  • update-translation-strings.yml
  • codeql.yml
  • claude-code-review.yml
  • claude.yml
  • close-incomplete-issues.yml
  • close-stale-issues.yml

As part of this housekeeping task, we should also validate the affected workflows against Node.js 24 early (for example by temporarily enabling FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true) so any compatibility issues can be caught before the platform switch becomes the default.

Justification

GitHub has announced that JavaScript actions will begin running on Node.js 24 by default starting June 2, 2026. Cleaning this up ahead of time will help us avoid CI surprises, keep our workflows healthy, and make the transition smoother for maintainers and contributors alike.

Note: lock-threads.yml does not appear to need changes at the moment, as dessant/lock-threads@v6.0.0 already runs on Node.js 24.

*Originally created by @pheus on 3/12/2026* ### Proposed Changes Review and update the GitHub Actions in workflows on `main` that are still running on deprecated Node.js 20, and bump them to versions that support Node.js 24 where available. The warning currently mentions: * `actions/checkout@v4` * `actions/setup-node@v4` * `actions/setup-python@v5` * `astral-sh/ruff-action@4919ec5cf1f49eff0871dbcea0da843445b837e6` While looking through the workflows on `main`, there are a few additional actions that should be included in scope as well: * `actions/create-github-app-token@v1` * `EndBug/add-and-commit@a94899bca583c204427a224a7af87c02f9b325d5` * `actions/stale@v9` (used in both `close-incomplete-issues.yml` and `close-stale-issues.yml`) Affected workflows currently include: * `ci.yml` * `update-translation-strings.yml` * `codeql.yml` * `claude-code-review.yml` * `claude.yml` * `close-incomplete-issues.yml` * `close-stale-issues.yml` As part of this housekeeping task, we should also validate the affected workflows against Node.js 24 early (for example by temporarily enabling `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true`) so any compatibility issues can be caught before the platform switch becomes the default. ### Justification GitHub has [announced that JavaScript actions will begin running on Node.js 24 by default starting June 2, 2026. Cleaning this up ahead of time will help us avoid CI surprises, keep our workflows healthy, and make the transition smoother for maintainers and contributors alike.](<https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/>) Note: `lock-threads.yml` does not appear to need changes at the moment, as `dessant/lock-threads@v6.0.0` already runs on Node.js 24.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/netbox#155