Skip to content

resyncing package-lock #168

resyncing package-lock

resyncing package-lock #168

Triggered via push July 20, 2024 10:38
Status Failure
Total duration 1m 5s
Artifacts

ci.yml

on: push
Build & Unit Test
57s
Build & Unit Test
Deploy Test
0s
Deploy Test
Package & Push Container
0s
Package & Push Container
Deploy Production
0s
Deploy Production
Build & Deploy Documentation
0s
Build & Deploy Documentation
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
Build & Unit Test
Process completed with exit code 133.
Build & Unit Test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build & Unit Test
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4, google-github-actions/auth@v0.7.3, actions/setup-node@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build & Unit 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/
Build & Unit 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/