chore(deps): Bump fuel-vm to 0.66.2 and fuel-core to 0.48.0 (#1707)
#7243
xgreenxci.yml
on: push
publish-crates-check
16s
setup-test-projects
58s
get-workspace-members
7s
verify-rust-version
8s
fetch-fuel-core
28s
Matrix: cargo-verifications
publish
0s
Annotations
18 errors and 45 warnings
|
publish-crates-check
It seems package 'fuels-core' modified since '0.76.0' so new version should be published
|
|
publish-crates-check
It seems package 'fuels-code-gen' modified since '0.76.0' so new version should be published
|
|
publish-crates-check
It seems package 'fuels-accounts' modified since '0.76.0' so new version should be published
|
|
cargo-verifications (nextest, run --all-targets --workspace --cargo-quiet --no-fail-fast, sway-ex...
Process completed with exit code 100.
|
|
cargo-verifications (check, --all-features, 'fuels-example-cookbook')
The strategy configuration was canceled because "cargo-verifications.nextest_run_--all-targe_2" failed
|
|
cargo-verifications (check, --all-features, 'fuels-example-cookbook')
The operation was canceled.
|
|
cargo-verifications (check_doc_unresolved_links)
The strategy configuration was canceled because "cargo-verifications.nextest_run_--all-targe_2" failed
|
|
cargo-verifications (check_doc_unresolved_links)
The operation was canceled.
|
|
cargo-verifications (check, --all-features, 'fuels')
The strategy configuration was canceled because "cargo-verifications.nextest_run_--all-targe_2" failed
|
|
cargo-verifications (check, --all-features, 'fuels')
The operation was canceled.
|
|
cargo-verifications (check, --all-features, 'e2e')
The strategy configuration was canceled because "cargo-verifications.nextest_run_--all-targe_2" failed
|
|
cargo-verifications (check, --all-features, 'e2e')
The operation was canceled.
|
|
cargo-verifications (check, --all-features, 'fuels-example-contracts')
The strategy configuration was canceled because "cargo-verifications.nextest_run_--all-targe_2" failed
|
|
cargo-verifications (check, --all-features, 'fuels-example-contracts')
The operation was canceled.
|
|
cargo-verifications (check, --all-features, 'fuels-test-helpers')
The strategy configuration was canceled because "cargo-verifications.nextest_run_--all-targe_2" failed
|
|
cargo-verifications (check, --all-features, 'fuels-test-helpers')
The operation was canceled.
|
|
cargo-verifications (nextest, run --all-targets --features "default fuel-core-lib coin-cache" --w...
The strategy configuration was canceled because "cargo-verifications.nextest_run_--all-targe_2" failed
|
|
cargo-verifications (nextest, run --all-targets --features "default fuel-core-lib coin-cache" --w...
The operation was canceled.
|
|
publish-crates-check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: FuelLabs/publish-crates@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
fetch-fuel-core
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
fetch-fuel-core
Failed to restore: Cache service responded with 404
|
|
setup-test-projects
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
setup-test-projects
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (fmt, --all --verbose -- --check)
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuels-example-types')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuels-example-providers')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuels-example-macros')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuels-example-debugging')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuels-example-codec')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'wasm-tests')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check_typos)
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (machete, --skip-target-dir)
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuels-example-wallets')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'check-docs')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuels-example-predicates')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check_doc_anchors_valid)
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuels-code-gen')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'versions-replacer')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuels-macros')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (test_wasm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
cargo-verifications (test_wasm)
Failed to save: some pre requistes not met
|
|
cargo-verifications (test_wasm)
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'change-log')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuels-example-rust-bindings')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuels-core')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuel-core-version')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuels-accounts')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuels-programs')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check_fuel_core_version)
Failed to save: some pre requistes not met
|
|
cargo-verifications (check_fuel_core_version)
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (clippy, --all-targets, sway-examples)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
cargo-verifications (clippy, --all-targets, sway-examples)
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (test, --doc --workspace)
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (nextest, run --all-targets --workspace --cargo-quiet --no-fail-fast, sway-ex...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
cargo-verifications (nextest, run --all-targets --workspace --cargo-quiet --no-fail-fast, sway-ex...
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuels-example-cookbook')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check_doc_unresolved_links)
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuels')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'e2e')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuels-example-contracts')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (check, --all-features, 'fuels-test-helpers')
Failed to restore: Cache service responded with 404
|
|
cargo-verifications (nextest, run --all-targets --features "default fuel-core-lib coin-cache" --w...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
cargo-verifications (nextest, run --all-targets --features "default fuel-core-lib coin-cache" --w...
Failed to restore: Cache service responded with 404
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
fuel-core
Expired
|
28.5 MB |
sha256:dcd15ed34c775f1fc906804e145de6dc69f31f525e00fcf86d46aebdb96739f2
|
|
|
sway-examples
Expired
|
350 KB |
sha256:0562a66efd4ed02d49ef2a75ff9e7769ed29f6b38c53f3cbf0a2ae770f762608
|
|