Skip to content

fix: Add missing core dependency to target-chrome-app (#489) #384

fix: Add missing core dependency to target-chrome-app (#489)

fix: Add missing core dependency to target-chrome-app (#489) #384

Triggered via push November 17, 2023 14:28
Status Success
Total duration 3m 38s
Artifacts

tests.yml

on: push
Unit tests
3m 19s
Unit tests
Static analysis
1m 17s
Static analysis
Integration tests: CLI
3m 26s
Integration tests: CLI
Visual tests: React DOM
2m 27s
Visual tests: React DOM
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Static analysis
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Visual tests: React DOM
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Unit tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Integration tests: CLI
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/