Hotfix - update angular & add OpenSSL legacy provider to workflow #1
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.
To solve the original problem (https://stackoverflow.com/questions/66028314/error-node-modules-callback-was-already-called) Angular was updated from 9.1.1 to 10.2.5.
The update lead under the used github-hosted runner ubuntu-latest, which used Node.js Version 18.20.0 to another problem (https://kinsta.com/de/wissensdatenbank/err_ossl_evp_unsupported/), which has been solved by declaring the environment variable in the workflow main.yml file according to actions/setup-node#356.
Please keep in mind to set the environment variable according to your os:
Windows: set NODE_OPTIONS=--openssl-legacy-provider
Linux / Mac: export NODE_OPTIONS=--openssl-legacy-provider