Skip to content

(#2) Upgrade CI and release workflows to Node 24-compatible GitHub Actions#1

Merged
vjanelle merged 1 commit into
mainfrom
codex/check-actions-compatibility-with-node.js-24
Mar 17, 2026
Merged

(#2) Upgrade CI and release workflows to Node 24-compatible GitHub Actions#1
vjanelle merged 1 commit into
mainfrom
codex/check-actions-compatibility-with-node.js-24

Conversation

@vjanelle
Copy link
Copy Markdown
Owner

Motivation

  • The CI and release workflows were using action versions that run on Node.js 20, which is being deprecated and can cause workflows to fail when GitHub defaults to Node.js 24.
  • The change aims to opt the workflows into Node.js 24 now and move to action major versions that support the newer runtime.

Description

  • Updated action versions in .github/workflows/ci.yml and .github/workflows/release.yml: actions/checkout@v4actions/checkout@v5, actions/setup-go@v5actions/setup-go@v6, actions/upload-artifact@v4actions/upload-artifact@v5, and actions/download-artifact@v4actions/download-artifact@v5 (release workflow).
  • Added a workflow-level environment variable FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true" to both CI and Release workflows to opt in to the Node.js 24 runtime.
  • No changes were made to job logic besides updating action versions and adding the opt-in environment variable.

Testing

  • Parsed all workflow YAML files with ruby -ryaml -e 'Dir[".github/workflows/*.yml"].each{|f| YAML.load_file(f); puts "ok #{f}" }' and all files loaded successfully.
  • Attempted a Python yaml.safe_load check but it failed due to PyYAML not being installed in the environment, so that validation was not run there.

Codex Task

@vjanelle vjanelle changed the title Upgrade CI and release workflows to Node 24-compatible GitHub Actions (#2) Upgrade CI and release workflows to Node 24-compatible GitHub Actions Mar 16, 2026
@vjanelle vjanelle merged commit f47ad09 into main Mar 17, 2026
7 of 9 checks passed
@vjanelle vjanelle deleted the codex/check-actions-compatibility-with-node.js-24 branch March 17, 2026 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant