Skip to content

Fix #10530 fix catalog editor for array scenario #2948

Fix #10530 fix catalog editor for array scenario

Fix #10530 fix catalog editor for array scenario #2948

Re-run triggered September 4, 2024 12:09
Status Failure
Total duration 9m 4s
Artifacts

CI.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
test-front-end
Process completed with exit code 1.
test-back-end
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-java@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build
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
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-java@v3, actions/setup-node@v2, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-front-end
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/