remove usage of 'core.addPath'

[alfredodeza]

The usage of core.addPath was causing the creation of add-path into the dist/index.js binary via ncc. By removing core.addPath there are no more warnings. The path is now used directly via the cache instead of just grype.

Closes #71

[alfredodeza]

@jonico I believe this one fixes the problem. Mind double checking the changes? I don't see the warnings anymore

[jonico]

@alfredodeza: While the code changes look ok to me, you could also just upgrade actions/core to 1.2.6: actions/toolkit#582

[alfredodeza]

@jonico thanks for the suggestion. The package.json file already declares actions/core at ^1.2.6, do you mean some other version? Any pointers would be great, because I do think that bumping that is a good idea as well!

[jonico]

@alfredodeza: weird, your package.json indicates that should already be at the right version of the package and still core.add-path uses the old syntax

Looking into the source of core.add-path

... could it be that for some reason the env GITHUB_PATH is not set properly in your action?

[alfredodeza]

@jonico I've updated actions/core locally and now the build properly shows the 1.2.6 version. Thanks for catching up. Would love a second look at the changes if you don't mind :) (I dropped the action changes now that 1.2.6 is being used)

[jonico]

🚢 it!

[jonico]