Skip to content

Using safe-singleton-factory for module deployment #310

Using safe-singleton-factory for module deployment

Using safe-singleton-factory for module deployment #310

Triggered via pull request August 5, 2024 09:26
@remedcuremedcu
synchronize #477
using-factory
Status Success
Total duration 55m 1s
Artifacts

certora_4337.yml

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

Annotations

4 warnings
verify (SignatureLengthCheck)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
verify (ValidationDataLastBitOne)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
verify (TransactionExecutionMethods)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
verify (Safe4337Module)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/