Fixing WASM-NPM packaging and publishing #3872

Triggered via pull request September 26, 2024 12:54

arboleya

synchronize #835

aa/fix/wasm-npm-packaging-and-publishing

Status Success

Total duration 15m 9s

Artifacts –

ci.yml

on: pull_request

publish-wasm-packages-check

13m 51s

Matrix: cargo

verifications-complete

Publish code coverage report on GitHub pages branch

2m 41s

publish

publish_wasm_packages

Annotations

9 errors and 67 warnings

publish-check

Unable to determine latest modification time for local package 'fuel-types' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-check

Unable to determine latest modification time for local package 'fuel-derive' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-check

Unable to determine latest modification time for local package 'fuel-merkle' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-check

Unable to determine latest modification time for local package 'fuel-asm' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-check

Unable to determine latest modification time for local package 'fuel-vm' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-check

Unable to determine latest modification time for local package 'fuel-storage' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-check

Unable to determine latest modification time for local package 'fuel-crypto' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-check

Unable to determine latest modification time for local package 'fuel-compression' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-check

Unable to determine latest modification time for local package 'fuel-tx' due to: 'TypeError: Cannot read properties of null (reading 'target')'

publish-check

The following actions uses node12 which is deprecated and will be forced to run on node16: FuelLabs/publish-crates@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

publish-check

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, FuelLabs/publish-crates@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 Changelog

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

cargo-toml-fmt-check

The following actions uses node12 which is deprecated and will be forced to run on node16: 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/

cargo-toml-fmt-check

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

cargo_audit

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, rustsec/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

cargo_audit

3 warnings found!

rustfmt

cargo (check, --all-targets -p fuel-storage)

cargo (check, --all-targets -p fuel-crypto)

cargo (check, --target wasm32-unknown-unknown -p fuel-crypto --no-default-features)

cargo (check, --target thumbv6m-none-eabi -p fuel-asm -p fuel-crypto -p fuel-storage -p fuel-merk...

cargo (check, --all-targets -p fuel-types)

cargo (check, --all-targets -p fuel-asm)

cargo (check, --target wasm32-unknown-unknown -p fuel-tx --features serde --no-default-features)

cargo (check, --all-targets -p fuel-merkle)

cargo (check, --target wasm32-unknown-unknown -p fuel-types --features serde --no-default-features)

cargo (rustc, --target wasm32-unknown-unknown -p fuel-types --features typescript --crate-type=cd...

cargo (check, --all-targets -p fuel-tx)

cargo (check, --all-targets --no-default-features)

cargo (check, --target wasm32-unknown-unknown -p fuel-vm --features alloc --no-default-features)

cargo (rustc, --target wasm32-unknown-unknown -p fuel-asm --features typescript --crate-type=cdylib)

cargo (check, --all-targets -p fuel-vm)

cargo (check, --all-targets --all-features)

cargo (make, check)

cargo (check, --all-targets)

cargo (clippy, --all-targets --all-features -- -D warnings -D clippy::dbg_macro)

cargo (bench, --workspace --no-run)

cargo (test, --all-targets --no-default-features --features serde)

cargo (test, --all-targets --features serde)

cargo (test, --all-targets --all-features)

cargo (test, --all-targets --no-default-features --features alloc)

cargo (test, --all-targets --features random,profile-gas,profile-coverage,serde)

cargo (test, --all-targets --features random)

cargo (test, --all-targets --no-default-features)

Publish code coverage report on GitHub pages branch

publish-wasm-packages-check

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/

publish-wasm-packages-check

Both node-version and node-version-file inputs are specified, only node-version will be used

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fixing WASM-NPM packaging and publishing #3872

Summary