Skip to content

Incorrect crypto version when scanning Go binary #1155

Incorrect crypto version when scanning Go binary

Incorrect crypto version when scanning Go binary #1155

Triggered via issue October 9, 2024 14:18
Status Success
Total duration 17s
Artifacts
Fit to window
Zoom out
Zoom in

Annotations

1 warning
run / Issue
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/add-to-project@31b3f3ccdc584546fc445612dec3f38ff5edb41c, titoportas/update-project-fields@421a54430b3cdc9eefd8f14f9ce0142ab7678751. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/