Skip to content
CI

feat: add new Option<CryptoProvider> to client configuration #255

Sign in to view logs

feat: add new Option<CryptoProvider> to client configuration

feat: add new Option<CryptoProvider> to client configuration #255

Triggered via pull request August 4, 2024 23:51
@oleonardolimaoleonardolima
synchronize #138
oleonardolima:expose-rust-cryptoprovider-to-user
Status Success
Total duration 4m 16s
Artifacts –

cont_integration.yml

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

Annotations

4 warnings
Test (stable)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test (stable)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test (1.63.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test (1.63.0)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/