GitHub Actions Node Version Bump

[BnJam]

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

[BnJam]

Starting work on this issue. I will investigate the GitHub Actions workflows for usages of Node.js 20 actions (actions/checkout@v4, actions/setup-python@v5), check for updated major versions that support Node.js 24, and bump them accordingly.

[BnJam]

Opened PR: #80

[BnJam]

technocore completed pipeline issue-handler.

Let me verify the latest versions of these actions and their Node 24 support.
Let me audit which actions in these workflows actually run on Node 20 by checking their action manifests.
Several more actions run on node20. Let me check the newest majors for the third-party and remaining first-party actions.
Let me check the repo's recent history and any related prior work to understand scope conventions.
The issue names exactly two actions. Let me verify the setup-python@v6 and checkout@v5 runtime and confirm no input/behavior changes that matter for these workflows.
Both bumps are runtime-only (node24) with unchanged inputs. Creating the fix branch and applying the changes.
All active lines updated; commented-out dead code left untouched. Verifying YAML validity:
No YAML parser available; the diff is version-string-only, so structure is preserved. Reviewing the final diff:
Done. PR opened at #80.

Fix summary:

• Bumped actions/checkout@v4 → @v5 and actions/setup-python@v5 → @v6 (both Node 24 runtimes, runtime-only changes) across all 4 workflow files: ci.yml, release.yml, static.yml, tag-release.yml (20 replacements; commented-out dead code in release.yml:240-300 left untouched).
• Verified the new majors' runtimes and unchanged inputs via their action.yml manifests.

[BnJam]

Starting work on this issue... I will inspect the GitHub Actions workflow files, identify usages of actions/checkout@v4 and actions/setup-python@v5 running on Node.js 20, and bump them to the latest available versions that support Node.js 24.

[BnJam]

Opened PR: #80

Investigation summary:

• actions/checkout@v4 (Node 20) is used in .github/workflows/ci.yml (lines 27, 105), static.yml (line 35), release.yml (lines 30, 138, 174, 212), tag-release.yml (lines 19, 42, 58, 77).
• actions/setup-python@v5 (Node 20) is used in ci.yml (lines 35, 111), static.yml (line 54), release.yml (lines 37, 180, 227), tag-release.yml (lines 44, 60, 91).
• Bumped actions/checkout@v4 -> @v5 (first major on Node 24 runtime, requires runner >= v2.327.1; GitHub-hosted runners qualify).
• Bumped actions/setup-python@v5 -> @v6 (first major on Node 24 runtime, same runner requirement).
• Also updated commented-out references in release.yml for consistency.

[BnJam]

Starting work on this issue...

[BnJam]

Resuming work on this issue. Auditing all GitHub Actions in .github/workflows for Node.js 20 runtimes, verifying Node 24-compatible majors via their action.yml manifests, and bumping each affected action.

[BnJam]

Updated PR: #80

Extended the fix to cover ALL Node 20 actions in the workflows (verified Node 24 runtimes via each action's action.yml): checkout v4->v5, setup-python v5->v6, upload-artifact v4->v6, download-artifact v4->v7, setup-uv v3->v7, setup-qemu-action v3->v4, upload-pages-artifact v3->v5, configure-pages v5->v6, deploy-pages v4->v5.

[BnJam]

technocore completed pipeline issue-handler.

Network is back. Let me read the current workflow files and verify the action versions.
Now let me verify the latest available versions of all actions in use against the GitHub API.
The GitHub API is authoritative here and shows newer majors exist than what's currently in the working tree. Let me check the reflog to understand the previous session's progress, and verify Node-24 support per action major.
Let me check if there's any existing PR or reference for this issue on the repo.
PR #80 already exists for this issue. Let me inspect it.
Let me verify the actual Node runtimes of the actions by fetching their action.yml manifests.
Verified ground truth. The uncommitted changes bump each action to its first Node-24 major (all confirmed via action.yml):

• upload-artifact@v4→v6, download-artifact@v4→v7, setup-uv@v3→v7, qemu@v3→v4, configure-pages@v5→v6, deploy-pages@v4→v5, upload-pages-artifact@v3→v5 (composite, latest)

This is consistent with the committed checkout@v4→v5 and setup-python@v5→v6. Let me confirm there are no other workflow files or actions I'm missing.
All workflow files verified. The diff is version-string-only, so YAML structure is preserved. Let me post the acknowledgment, then commit the pending changes.
Now push and update the existing PR #80.
Done. PR #80 now contains the complete fix for issue #79.

What was done:

• Audited all 4 workflows (.github/workflows/{ci,release,static,tag-release}.yml) for Node 20 actions.
• Verified Node 24 runtimes for every candidate major directly via each action's action.yml (runs.using), not guesses.
• Bumped every Node 20 action to its first Node-24 major: checkout@v4→v5, setup-python@v5→v6, upload-artifact@v4→v6, download-artifact@v4→v7, setup-uv@v3→v7, setup-qemu-action@v3→v4, upload-pages-artifact@v3→v5, configure-pages@v5→v6, deploy-pages@v4→v5 (incl. commented refs in release.yml).
• Pushed technocore/issue-79-fix (HEAD 5c65c7c), updated PR fix(ci): bump GitHub Actions to Node 24 runtimes #80 body, and posted the PR URL on the issue. PR is open and mergeable.