Skip to content

chore(ci): upgrade workflow actions to Node 24 - #7

Merged
m17kea merged 1 commit into
mainfrom
codex/upgrade-actions-node24
Jul 16, 2026
Merged

m17kea merged 1 commit into
mainfrom
codex/upgrade-actions-node24

Conversation

@m17kea

@m17kea m17kea commented Jul 16, 2026

Copy link
Copy Markdown

Context

GitHub now forces actions using the deprecated Node 20 runtime onto Node 24 and emits warnings on every Symphony test and publish run.

TL;DR

Upgrade workflow actions to native Node 24 releases while retaining immutable SHA pins.

Summary

  • Upgrade actions/checkout from v4 to v7.0.0 in every workflow.
  • Upgrade actions/cache from v4 to v6.1.0.
  • Upgrade jdx/mise-action from v3 to v4.2.0.
  • Keep actions/create-github-app-token v3.2.0, which already uses Node 24.

Alternatives

  • Relying on GitHub's forced compatibility mode was rejected because it retains warnings and future runtime risk.
  • Floating major-version tags were rejected in favour of immutable release commit pins.

Test Plan

  • COLUMNS=240 LINES=60 make -C elixir all
  • actionlint -config-file .github/actionlint.yaml

Summary:
- upgrade checkout, cache, and mise actions to Node 24 releases
- retain immutable full-SHA pins across all Symphony workflows

Rationale:
- remove GitHub's Node 20 deprecation warnings before forced runtime
  compatibility becomes a failure risk
- use the current action releases supported by hosted runners

Tests:
- COLUMNS=240 LINES=60 make -C elixir all
- actionlint -config-file .github/actionlint.yaml

Co-authored-by: Codex <codex@openai.com>
@m17kea
m17kea merged commit 67cfba7 into main Jul 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant