Skip to content

[EVM-Equivalence-YUL] Implement evmCodeHash without mapping #3161

[EVM-Equivalence-YUL] Implement evmCodeHash without mapping

[EVM-Equivalence-YUL] Implement evmCodeHash without mapping #3161

Triggered via pull request August 28, 2024 14:12
Status Success
Total duration 4m 20s
Artifacts

l1-contracts-ci.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

20 warnings
check-verifier-generator
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
check-verifier-generator
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check-verifier-generator
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
check-verifier-generator
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
check-verifier-generator
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
check-verifier-generator
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
lint
The following actions use a deprecated Node.js version and will be forced to run on node20: 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/
lint: l1-contracts/contracts/bridge/L1ERC20Bridge.sol#L33
Immutable variables name are set to be in capitalized SNAKE_CASE
lint: l1-contracts/contracts/bridge/L1ERC20Bridge.sol#L89
Use Custom Errors instead of require statements
lint: l1-contracts/contracts/bridge/L1ERC20Bridge.sol#L90
Use Custom Errors instead of require statements
lint: l1-contracts/contracts/bridge/L1ERC20Bridge.sol#L92
Use Custom Errors instead of require statements
lint: l1-contracts/contracts/bridge/L1ERC20Bridge.sol#L94
Use Custom Errors instead of require statements
lint: l1-contracts/contracts/bridge/L1ERC20Bridge.sol#L186
Use Custom Errors instead of require statements
lint: l1-contracts/contracts/bridge/L1ERC20Bridge.sol#L188
Use Custom Errors instead of require statements
lint: l1-contracts/contracts/bridge/L1ERC20Bridge.sol#L196
Avoid to use tx.origin
lint: l1-contracts/contracts/bridge/L1ERC20Bridge.sol#L272
Use Custom Errors instead of require statements
lint: l1-contracts/contracts/bridge/L1ERC20Bridge.sol#L275
Use Custom Errors instead of require statements
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/cache/save@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-hardhat
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/cache/restore@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-foundry
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/cache/restore@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/