Skip to content
Back to pull request #537

[SDK-3862] Add sync support using unasync #772

Sign in to view logs

[SDK-3862] Add sync support using unasync

[SDK-3862] Add sync support using unasync #772

Triggered via pull request October 9, 2023 15:33
@owenpearsonowenpearson
synchronize #537
feature/add-sync-using-unasync
Status Success
Total duration 16m 40s
Artifacts –

check.yml

on: pull_request
Matrix: check
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
check (3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
check (3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
check (3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
check (3.7)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/