JFrog tasks dependent on Node 20 (EOL April 2026); Request Node 24 support #587
Description
Describe the bug
Azure Pipelines agents have transitioned to the Node 24 runtime (Jan 2026). However, the JFrog Azure DevOps extension tasks are still declaring the Node 20 (and in some cases Node 16) execution handlers.
With Node 20 reaching official End-of-Life on April 30, 2026, organizations using these tasks will face security compliance failures and deprecation warnings within their CI/CD environments.
Current behavior
When running JFrog tasks (e.g., jfrogGenericArtifacts@1) on modern agents, the agent falls back to the Node 20 runner despite Node 24 being the primary supported runtime.
Task : jfrogGenericArtifacts
Version : 1.12.17
##[debug]Using node path: /home/azagent/externals/node20_1/bin/node
This task is dependent on a Node version (20) that is nearing end-of-life.
Reproduction steps
Use an Azure DevOps agent with version 4.x or later.
2. Run any JFrog task (e.g., JFrogToolsInstaller@1 or JFrogCliV2@1).
3. Check the "Initialize Job" or "Debug" logs to see the Node runner being invoked.
Expected behavior
The tasks should include a Node24 execution handler in their task.json to ensure they run on a supported, non-EOL runtime.
Azure DevOps extension name and version
• Extension Name: JFrog Azure DevOps Extension
• Version: latest
Operating system type and version
• (both Linux and Windows latest)
Why this is critical (Internal Note for JFrog)
Node 20 EOL is April 30, 2026. Many enterprise security policies (and Microsoft's own hosted agents) will begin strictly flagging or disabling EOL runtimes shortly after this date. This update is required to ensure pipeline stability and security compliance for all JFrog extension users.
Azure DevOps extension name and version
Jfrog 2.12.7
JFrog CLI version
1.12.7
Operating system type and version
Rhel 9.7
JFrog Artifactory version (if relevant)
7.127.0 cloud saas
JFrog Xray version (if relevant)
No response
JFrog Distribution version (if relevant)
2.12.7