Skip to content
PR Workflow

Create threats.yaml for Container Registry #141

Sign in to view logs

Create threats.yaml for Container Registry

Create threats.yaml for Container Registry #141

Triggered via pull request November 14, 2024 19:20
@kazmik23kazmik23
synchronize #527
kazmik23:patch-29
Status Failure
Total duration 24s
Artifacts –

pull_request.yaml

on: pull_request
run-format-check  /  prettier-fmt-check
6s
run-format-check / prettier-fmt-check
run-linting-check  /  markdown-lint
6s
run-linting-check / markdown-lint
link-checker  /  link-checker
9s
link-checker / link-checker
yaml-checker  /  yaml-check
3s
yaml-checker / yaml-check
todo-checker  /  find-todos
15s
todo-checker / find-todos
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
Property controls is not allowed. yaml-schema: file:///schemas/threats-schema.json.: services/devtools/ContainerReg/threats.yaml#L23
Property controls is not allowed.
Property controls is not allowed. yaml-schema: file:///schemas/threats-schema.json.: services/devtools/ContainerReg/threats.yaml#L37
Property controls is not allowed.
yaml-checker / yaml-check
1 file(s) failed validation
yaml-checker / yaml-check
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
run-format-check / prettier-fmt-check
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
run-linting-check / markdown-lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/