Skip to content

Fix issue with blueprint names and policy references #173

Fix issue with blueprint names and policy references

Fix issue with blueprint names and policy references #173

Triggered via push October 11, 2024 12:13
Status Failure
Total duration 3m 0s
Artifacts
Matrix: getting_started
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
getting_started (PY38_BC, 3.8)
Process completed with exit code 8.
getting_started (PY311_BC, 3.11)
Process completed with exit code 8.
getting_started (PY38_BC, 3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
getting_started (PY38_BC, 3.8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
getting_started (PY311_BC, 3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
getting_started (PY311_BC, 3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/