Skip to content

Fix node 20 configuration - #193

Open
ederpf wants to merge 1 commit into
dependency-check:mainfrom
ederpf:bug/fix-node20-configuration
Open

Fix node 20 configuration#193
ederpf wants to merge 1 commit into
dependency-check:mainfrom
ederpf:bug/fix-node20-configuration

Conversation

@ederpf

@ederpf ederpf commented Dec 24, 2025

Copy link
Copy Markdown

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-guidance

image

I 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.json is incorrect for Node 20. Azure Pipelines expects Node20_1, not Node20.

@Saturate

Copy link
Copy Markdown
Collaborator

We've got some pipeline trouble, and I don't have access. But does this do the same as #185 ?

@ederpf

ederpf commented Dec 26, 2025

Copy link
Copy Markdown
Author

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.

@Saturate

Copy link
Copy Markdown
Collaborator

Our pipeline is not building, and I don't have access. So there's not much I can do alone unfortunately.

@bm-fez bm-fez mentioned this pull request Jun 18, 2026
@bm-fez

bm-fez commented Jun 18, 2026

Copy link
Copy Markdown

Any progress on getting this merged?

@sicil1ano

Copy link
Copy Markdown

@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?

@Saturate

Copy link
Copy Markdown
Collaborator

Any progress on getting this merged?

Nope :) Go no access unfortunately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants