Skip to content

fix: matchers type is making the global expect unsafe #216

fix: matchers type is making the global expect unsafe

fix: matchers type is making the global expect unsafe #216

Triggered via pull request August 17, 2023 17:06
Status Failure
Total duration 1m 8s
Artifacts

validate.yml

on: pull_request
Matrix: main
release
0s
release
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 4 warnings
main (18)
Process completed with exit code 1.
main (20)
The job was canceled because "_18" failed.
main (20)
Process completed with exit code 1.
main (16)
Process completed with exit code 1.
main (14)
The operation was canceled.
main (18)
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/
main (20)
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/
main (16)
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/
main (14)
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/