Skip to content
CI

Fixing "next match" feature #13257

Sign in to view logs

Fixing "next match" feature

Fixing "next match" feature #13257

Triggered via pull request November 9, 2023 00:16
@varCepheidvarCepheid
synchronize #1498
fixing-next-match
Status Success
Total duration 1m 13s
Artifacts –

ci.yml

on: pull_request
build
1m 0s
build
lint
52s
lint
test
47s
test
typecheck
45s
typecheck
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
typecheck
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
lint
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. 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 uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/