Added support for new Node.js versions to resolve warning shown during execution of extension task.

[sicil1ano]

It addresses issue #179.

[sicil1ano]

Also wanted to ask what Node versions we expect to support. I haven't removed support for Node.js 10 and 16, but I think it would be reasonable for people to use a task that does not use Node.js versions that are marked as end-of-life.
Node.js 20 will certainly bring benefits, but users will also need to upgrade their agents to support the new version of the task.
It's been 2 years since Node.js 16 received the last update.
All of this means removing support for Node.js 10 and 16, and updating requirements to have Node.js 20 at minimum.

Any thoughts?

https://nodejs.org/en/about/previous-releases

[Saturate]

Also wanted to ask what Node versions we expect to support. I haven't removed support for Node.js 10 and 16, but I think it would be reasonable for people to use a task that does not use Node.js versions that are marked as end-of-life. Node.js 20 will certainly bring benefits, but users will also need to upgrade their agents to support the new version of the task. It's been 2 years since Node.js 16 received the last update. All of this means removing support for Node.js 10 and 16, and updating requirements to have Node.js 20 at minimum.

Any thoughts?

https://nodejs.org/en/about/previous-releases

I'd say we shouldn't support things that are EOL. But if it's causing us no problems supporting it for now, we can let it be as it.

[Saturate]

Thanks for this :)

[ederpf]

Thank you for contributing with the repository @sicil1ano : )

I am using in DevOps yaml pipeline, the task "dependency-check-build-task@6" that shows the warning you fixed.
I have updated the version to "dependency-check-build-task@6.3.0" but it shows the same warning. Do you know if something more should be updated in the repo?

Thank you,
Eder

[Saturate]

We need to merge this: #185 but the pipeline is not working, and I don't have access.