What would you like to be added:
Reduce the dependency on the deprecated Node.js 20 runtime in Karmada GitHub Actions workflows.
The Node.js 20 deprecation warning has appeared in multiple workflow runs across master and maintained release branches:
-
master
-
release-1.18
-
release-1.17
-
release-1.16
The expected work is to audit the workflows/actions that still rely on Node.js 20 and reduce that dependency. For each affected action:
- If the action has a newer version that no longer depends on Node.js 20, upgrade to that version.
- If the action is no longer maintained or has no suitable update, replace it with another maintained action.
- If no appropriate replacement exists, implement the required logic directly in the workflow or repository scripts.
This should be applied consistently to master and affected release branches where applicable.
Why is this needed:
GitHub Actions has started warning about the deprecation of the Node.js 20 runtime. If Karmada continues to rely on actions that execute with Node.js 20, these workflows may eventually become unstable or fail when GitHub further restricts or removes support for that runtime.
Reducing the Node.js 20 dependency ahead of time helps keep CI and release workflows maintainable across active branches, avoids future disruption, and removes reliance on outdated or unmaintained GitHub Actions.
What would you like to be added:
Reduce the dependency on the deprecated Node.js 20 runtime in Karmada GitHub Actions workflows.
The Node.js 20 deprecation warning has appeared in multiple workflow runs across
masterand maintained release branches:masterrelease-1.18release-1.17release-1.16The expected work is to audit the workflows/actions that still rely on Node.js 20 and reduce that dependency. For each affected action:
This should be applied consistently to
masterand affected release branches where applicable.Why is this needed:
GitHub Actions has started warning about the deprecation of the Node.js 20 runtime. If Karmada continues to rely on actions that execute with Node.js 20, these workflows may eventually become unstable or fail when GitHub further restricts or removes support for that runtime.
Reducing the Node.js 20 dependency ahead of time helps keep CI and release workflows maintainable across active branches, avoids future disruption, and removes reliance on outdated or unmaintained GitHub Actions.