Removed content_security_policy_nonce_in setting from talisman config #163
Triggered via pull request
September 9, 2024 14:27
NikolayBorovenskiy
Status
Success
Total duration
20m 15s
Artifacts
–
Annotations
2 errors and 4 warnings
|
unit-tests (3.10)
Process completed with exit code 1.
|
|
unit-tests (3.9)
Process completed with exit code 1.
|
|
unit-tests (3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: ./.github/actions/cached-dependencies. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
unit-tests (3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, ./.github/actions/cached-dependencies. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
unit-tests (3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: ./.github/actions/cached-dependencies. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
unit-tests (3.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, ./.github/actions/cached-dependencies. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|