Skip to content

Adds unsafe-inline property to talisman content security policy setting #74

Adds unsafe-inline property to talisman content security policy setting

Adds unsafe-inline property to talisman content security policy setting #74

Triggered via pull request September 9, 2024 13:26
Status Success
Total duration 1m 9s
Artifacts

superset-helm-lint.yml

on: pull_request
lint-test
45s
lint-test
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
lint-test
The following actions uses node12 which is deprecated and will be forced to run on node16: azure/setup-helm@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
lint-test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, azure/setup-helm@v1, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
lint-test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
lint-test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/