Fix node 20 configuration - #193
Conversation
|
We've got some pipeline trouble, and I don't have access. But does this do the same as #185 ? |
|
Hi @Saturate , thank you for the quick response. Yes, we could go with that PR instead mine. Keeping only node20, it will fix the warning and it does not make sense to keep EOL versions that can generate noise. Do you think if that PR can be merged? We can close this one. |
|
Our pipeline is not building, and I don't have access. So there's not much I can do alone unfortunately. |
|
Any progress on getting this merged? |
|
@pippolino Can you grant rights to @Saturate to review/approve pipelines and anything else that would allow this project to carry on? Who do we need to contact in case you cannot do that? |
Nope :) Go no access unfortunately. |
While running "dependency-check-build-task@6" task on an Azure DevOps pipeline this warning is shown:
##[warning]Task 'OWASP Dependency Check' version 6 (dependency-check-build-task@6) is dependent on a Node version (16) that is end-of-life. Contact the extension owner for an updated version of the task. Task maintainers should review Node upgrade guidance: https://aka.ms/node-runner-guidanceI noticed that the task is configured to run on Node 10, Node 16, and Node 20, but Node 20 is not working. After doing some research, I found that the reason it still uses Node 16 is that the handler name in
task.jsonis incorrect for Node 20. Azure Pipelines expectsNode20_1, notNode20.