Skip to content

feat: setup configuration for upcoming hard fork and re-enable sha256 precompile #2742

feat: setup configuration for upcoming hard fork and re-enable sha256 precompile

feat: setup configuration for upcoming hard fork and re-enable sha256 precompile #2742

Triggered via pull request November 15, 2023 13:11
Status Success
Total duration 3m 24s
Artifacts

l2geth_ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
goimports-lint
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-mock-ccc-geth
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/checkout@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
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
check
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/