Fix node 20 configuration#193
Open
ederpf wants to merge 1 commit intodependency-check:mainfrom
Open
Conversation
ederpf
requested review from
a team,
Saturate,
alxmancini,
pippolino and
tlogik
as code owners
Collaborator
|
We've got some pipeline trouble, and I don't have access. But does this do the same as #185 ? |
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. |
Collaborator
|
Our pipeline is not building, and I don't have access. So there's not much I can do alone unfortunately. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.