Skip to content
Container Images

fix: issue where custom-networks defaulted to forked-providers when they were not forked networks. #109

Sign in to view logs

fix: issue where custom-networks defaulted to forked-providers when they were not forked networks.

fix: issue where custom-networks defaulted to forked-providers when they were not forked networks. #109

Triggered via pull request August 23, 2024 15:20
@antazoeyantazoey
synchronize #2239
antazoey:fix/forked-provider-added-to-non-forked-custom-network
Status Success
Total duration 3m 16s
Artifacts –

build.yaml

on: pull_request
build
3m 5s
build
Fit to window
Zoom out
Zoom in

Annotations

1 warning
build
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/build-push-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/