Skip to content

fix: use cached deployedBytecode where possible #143

fix: use cached deployedBytecode where possible

fix: use cached deployedBytecode where possible #143

Triggered via push July 3, 2024 18:10
Status Failure
Total duration 5m 47s
Artifacts
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
py311core
Process completed with exit code 1.
py311core
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
py311core
The following actions uses Node.js version which is deprecated and will be forced to run on node20: 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/