fix: forc build panic when sway package folder contains dot
#17375
Halimao
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
ci.yml
on: pull_request
build-sway-lib-core
3m 30s
build-sway-lib-std
3m 50s
build-sway-examples
3m 54s
build-forc-test-project
7m 36s
cargo-build-workspace
6m 9s
cargo-clippy
3m 32s
cargo-fmt-check
13s
cargo-run-e2e-test
18m 16s
cargo-run-e2e-test-evm
4m 52s
cargo-test-lib-std
6m 53s
cargo-test-workspace
16m 46s
cargo-unused-deps-check
6m 52s
pre-publish-check
0s
build-reference-examples
3m 43s
forc-fmt-check-sway-lib-core
3m 25s
forc-fmt-check-sway-lib-std
3m 37s
forc-fmt-check-sway-examples
3m 20s
forc-fmt-check-panic
4m 3s
build-mdbook
8m 46s
build-forc-doc-sway-lib-std
4m 41s
cargo-toml-fmt-check
17s
cargo-run-e2e-test-midenvm
5m 2s
forc-run-benchmarks
5m 13s
forc-unit-tests
4m 13s
forc-pkg-fuels-deps-check
2m 40s
notify-slack-on-failure
3s
build-publish-master-image
0s
build-publish-release-image
0s
Matrix: Build and upload forc binaries to release
Annotations
1 warning
|
cargo-toml-fmt-check
The following actions uses node12 which is deprecated and will be forced to run on node16: baptiste0928/cargo-install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|