Skip to content

Support specifying custom Scarb.lock path #112

Support specifying custom Scarb.lock path

Support specifying custom Scarb.lock path #112

Triggered via pull request October 9, 2024 15:27
Status Failure
Total duration 36s
Artifacts

ci.yml

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

Annotations

5 errors and 4 warnings
lint
Process completed with exit code 1.
test windows-latest
There was an error when restoring cache: failed to find Scarb.lock
test windows-latest
Process completed with exit code 1.
test macos-latest
There was an error when restoring cache: failed to find Scarb.lock
test ubuntu-latest
There was an error when restoring cache: failed to find Scarb.lock
lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test windows-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test macos-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test ubuntu-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/