Every CI job logs this, on both workflows:
Node 20 is being deprecated. This workflow is running with Node 24 by default.
If you need to temporarily use Node 20, you can set the
ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable.
and at job end:
##[warning]Node.js 20 is deprecated. The following actions target Node.js 20
but are being forced to run on Node.js 24: actions/checkout@v4,
actions/setup-python@v5
Currently harmless — GitHub is silently running them on Node 24 and everything passes. But the compatibility shim is explicitly temporary, and when it goes the affected actions stop working. That would break ci.yml and tla.yml simultaneously and for a reason unrelated to any change in this repo, which is an unpleasant way to discover it.
Actions to bump:
actions/checkout@v4 → @v5actions/setup-python@v5 → @v6actions/setup-java@v4 (in tla.yml) — worth checking whether it is affected too
Low urgency, low risk, but it is the kind of thing that is trivial to do now and annoying to do under pressure later. Worth confirming the newer majors do not change any behaviour these workflows rely on before bumping.
Noticed while reading CI logs during #64/#65.
Every CI job logs this, on both workflows:
and at job end:
Currently harmless — GitHub is silently running them on Node 24 and everything passes. But the compatibility shim is explicitly temporary, and when it goes the affected actions stop working. That would break
ci.ymlandtla.ymlsimultaneously and for a reason unrelated to any change in this repo, which is an unpleasant way to discover it.Actions to bump:
actions/checkout@v4→@v5actions/setup-python@v5→@v6actions/setup-java@v4(intla.yml) — worth checking whether it is affected tooLow urgency, low risk, but it is the kind of thing that is trivial to do now and annoying to do under pressure later. Worth confirming the newer majors do not change any behaviour these workflows rely on before bumping.
Noticed while reading CI logs during #64/#65.