You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b187bb5
Browse filesBrowse the repository at this point in the historyBrowse files
GitHub now forces actions that target Node.js 20 onto Node 24 and logs
a deprecation warning on every job. When Node 20 support is removed,
every PR and merge-queue leg that sets up Node or Python, or moves an
artifact, would break at the same moment.
Move the CI workflow and the two artifact retry composites to the
first release of each action that runs on Node 24. Each new pin's only
breaking change is the runtime, or an input we don't use:
- setup-node v4 -> v6.4.0 (pin already used in release.yml; no
root package.json, so the v5+ auto-cache never turns on)
- setup-python v5 -> v6.3.0
- download-artifact v4 -> v7.0.0 (we download by pattern, not ID)
- upload-artifact v4 -> v6.0.0
- setup-uv v6.8.0 -> v7.0.0 (drops only the unused server-url)
release.yml and the disabled compatibility workflows are left alone.
Refs #1588
Assisted-by: Claude Code:claude-opus-5-5
0 commit comments