Why is this needed?
Node 16 is still in use by Frogbot (action.yml declares using: "node16") and is deprecated by GitHub. The previous attempt to upgrade to Node 20 in #770 was closed without merging, and Node 20 itself reaches end-of-life in April 2026. To avoid another short-lived upgrade, this proposes jumping straight to Node 24 (the current LTS line).
What needs to be changed?
action.yml: using: "node16" → using: "node24"action/package.json and action/package-lock.json: "node": ">=16.0.0" → ">=24.0.0".github/workflows/action-test.yml and .github/workflows/test.yml: bump setup-node node-version from 16 to 24docs/templates/jfrog-pipelines/pipelines-npm.yml and pipelines-yarn2.yml: bump runtime image version: "16" → "24"
Related
Why is this needed?
Node 16 is still in use by Frogbot (
action.ymldeclaresusing: "node16") and is deprecated by GitHub. The previous attempt to upgrade to Node 20 in #770 was closed without merging, and Node 20 itself reaches end-of-life in April 2026. To avoid another short-lived upgrade, this proposes jumping straight to Node 24 (the current LTS line).What needs to be changed?
action.yml:using: "node16"→using: "node24"action/package.jsonandaction/package-lock.json:"node": ">=16.0.0"→">=24.0.0".github/workflows/action-test.ymland.github/workflows/test.yml: bumpsetup-nodenode-versionfrom16to24docs/templates/jfrog-pipelines/pipelines-npm.ymlandpipelines-yarn2.yml: bump runtime imageversion: "16"→"24"Related