Skip to content
main

fix: KeyMatch5 does not match the expected result (#458) #433

Sign in to view logs

fix: KeyMatch5 does not match the expected result (#458)

fix: KeyMatch5 does not match the expected result (#458) #433

Triggered via push September 19, 2023 15:24
@hsluoyzhsluoyz
pushed 0df458d
master
Status Success
Total duration 2m 51s
Artifacts –

main.yml

on: push
Matrix: test
semantic-release
1m 26s
semantic-release
finish
3s
finish
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
test (^18)
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 (^16)
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 (^14)
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/
semantic-release
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/