Protect against passing i128::MIN
to abs()
which causes overflow
#9469
Triggered via pull request
September 24, 2024 15:15
Status
Success
Total duration
43m 43s
Artifacts
–
ci.yml
on: pull_request
verify-tag-version
0s
publish-crates-check
23s
cargo-audit
22s
Matrix: cargo-verifications
cargo-test-kms
6m 47s
Publish code coverage report on GitHub pages branch
25m 21s
publish-docker-image-profiling
14m 21s
publish-e2e-client-docker-image
2m 14s
publish-crates
0s
Matrix: Release fuel-core binaries
deploy-eph-env
0s
Annotations
10 errors and 100 warnings
publish-crates-check
Unable to determine latest modification time for local package 'fuel-gas-price-algorithm' due to: 'TypeError: Cannot read properties of null (reading 'target')'
|
publish-crates-check
Unable to determine latest modification time for local package 'fuel-core-storage' due to: 'TypeError: Cannot read properties of null (reading 'target')'
|
publish-crates-check
Unable to determine latest modification time for local package 'fuel-core-chain-config' due to: 'TypeError: Cannot read properties of null (reading 'target')'
|
publish-crates-check
Unable to determine latest modification time for local package 'fuel-core-types' due to: 'TypeError: Cannot read properties of null (reading 'target')'
|
publish-crates-check
Unable to determine latest modification time for local package 'fuel-core-consensus-module' due to: 'TypeError: Cannot read properties of null (reading 'target')'
|
publish-crates-check
Unable to determine latest modification time for local package 'fuel-core-producer' due to: 'TypeError: Cannot read properties of null (reading 'target')'
|
publish-crates-check
Unable to determine latest modification time for local package 'fuel-core-importer' due to: 'TypeError: Cannot read properties of null (reading 'target')'
|
publish-crates-check
Unable to determine latest modification time for local package 'fuel-core-executor' due to: 'TypeError: Cannot read properties of null (reading 'target')'
|
publish-crates-check
Unable to determine latest modification time for local package 'fuel-core-relayer' due to: 'TypeError: Cannot read properties of null (reading 'target')'
|
publish-crates-check
Unable to determine latest modification time for local package 'fuel-core-txpool' due to: 'TypeError: Cannot read properties of null (reading 'target')'
|
prevent-openssl
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/
|
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/
|
lint-toml-files
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/
|
rustfmt
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/
|
publish-crates-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-crates-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/
|
cargo-verifications (check, -p fuel-core-storage --target wasm32-unknown-unknown --no-default-fea...
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-audit
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/audit-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
cargo-audit
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions-rs/audit-check@v1. 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!
|
cargo-audit
Unknown warning kind unsound found, please, file a bug
|
cargo-verifications (check, -p fuel-core-types --target wasm32-unknown-unknown --no-default-featu...
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-verifications (check, -p fuel-core-executor --target wasm32-unknown-unknown --no-default-fe...
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-verifications (check, -p fuel-core-chain-config --target wasm32-unknown-unknown --no-defaul...
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-verifications (clippy, -p fuel-core-wasm-executor --target wasm32-unknown-unknown --no-defa...
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-verifications (test, -p fuel-core-chain-config --no-default-features)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-verifications (check, -p fuel-core-client --target wasm32-unknown-unknown --no-default-feat...
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-verifications (test, -p fuel-core-client --no-default-features)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-verifications (doc, --all-features --workspace --no-deps)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-verifications (make, check --locked)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-verifications (clippy, --all-targets --all-features)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-verifications (check, --all-targets)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-verifications (build, -p fuel-core-bin --no-default-features --features production)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-verifications (check, --manifest-path version-compatibility/Cargo.toml --workspace && cargo...
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-verifications (test, -p fuel-core --no-default-features)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-verifications (test, -p fuel-core --lib executor --features wasm-executor, FUEL_ALWAYS_USE_...
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-verifications (test, --workspace)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-verifications (test, --all-features --workspace)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-e2e-client-docker-image
The following actions uses node12 which is deprecated and will be forced to run on node16: docker/metadata-action@v3, docker/setup-buildx-action@v1, docker/login-action@v1, docker/build-push-action@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
publish-e2e-client-docker-image
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/metadata-action@v3, docker/setup-buildx-action@v1, docker/login-action@v1, docker/login-action@v2, docker/build-push-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
publish-e2e-client-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-e2e-client-docker-image
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
cargo-test-kms
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, buildjet/cache@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-docker-image
The following actions uses node12 which is deprecated and will be forced to run on node16: docker/metadata-action@v3, docker/setup-buildx-action@v1, docker/login-action@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-docker-image
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/metadata-action@v3, docker/setup-buildx-action@v1, docker/login-action@v1, docker/login-action@v2, 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/
|
publish-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The following actions uses node12 which is deprecated and will be forced to run on node16: docker/metadata-action@v3, docker/setup-buildx-action@v1, docker/login-action@v1, docker/build-push-action@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
publish-docker-image-profiling
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/metadata-action@v3, docker/setup-buildx-action@v1, docker/login-action@v1, docker/build-push-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
publish-docker-image-profiling
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-docker-image-profiling
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Publish code coverage report on GitHub pages branch
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/
|