[ci] Fix bug where rustup output was piped to jq
#9861
joshlfci.yml
on: pull_request
Generate cache
9s
Run tests under Kani
1m 6s
Check that all toolchains listed in Cargo.toml are tested in CI
37s
Check all-jobs-succeeded depends on all jobs
36s
Check for todo comments
17s
Run Git hooks
53s
zizmor
0s
Matrix: build_test
Run codegen tests
54s
Generate code coverage
53s
Build (zerocopy / nightly / --simd / aarch64_be-unknown-linux-gnu)
51s
Build (zerocopy / nightly / --simd / avr-none)
54s
Check Rust formatting
26s
Check stale stderr files
9s
Check GitHub Actions
54s
Check README.md
39s
Check crate versions match
12s
Check MSRV is minimal
13s
All checks succeeded
0s
Annotations
184 errors and 94 warnings
|
Check README.md
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / nightly / / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / nightly / / x86_64-pc-windows-msvc)
The operation was canceled.
|
|
Build & Test (zerocopy-derive / stable / / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy-derive / stable / / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / stable / --no-default-features / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / stable / --no-default-features / x86_64-pc-windows-msvc)
The operation was canceled.
|
|
Run Git hooks
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Run Git hooks
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-diagnostic-on-unimplemented-1-78-0 / --no-default-features / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / no-zerocopy-diagnostic-on-unimplemented-1-78-0 / / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / stable / / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-diagnostic-on-unimplemented-1-78-0 / / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / stable / / x86_64-pc-windows-msvc)
The operation was canceled.
|
|
Build & Test (zerocopy / msrv / --no-default-features / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy-derive / stable / / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-generic-bounds-in-const-fn-1-61-0 / --no-default-features / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / msrv / --no-default-features / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy-derive / stable / / x86_64-pc-windows-msvc)
The operation was canceled.
|
|
|
|
Build & Test (zerocopy / stable / --features __internal_use_only_features_that_work_on_stable / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy-derive / msrv / / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy-derive / msrv / / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / / x86_64-pc-windows-msvc)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-generic-bounds-in-const-fn-1-61-0 / / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-generic-bounds-in-const-fn-1-61-0 / / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / nightly / / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / nightly / / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / nightly / --features __internal_use_only_features_that_work_on_stable / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / stable / / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / stable / / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / stable / --no-default-features / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / stable / --no-default-features / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-core-error-1-81-0 / --no-default-features / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-core-error-1-81-0 / --no-default-features / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / --no-default-features / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / --no-default-features / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-core-error-1-81-0 / / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-core-error-1-81-0 / / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / no-zerocopy-diagnostic-on-unimplemented-1-78-0 / / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-diagnostic-on-unimplemented-1-78-0 / / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-generic-bounds-in-const-fn-1-61-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / nightly / --no-default-features / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / nightly / --no-default-features / x86_64-pc-windows-msvc)
The operation was canceled.
|
|
Build & Test (zerocopy-derive / stable / / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-core-error-1-81-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy-derive / stable / / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-diagnostic-on-unimplemented-1-78-0 / --no-default-features / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / no-zerocopy-diagnostic-on-unimplemented-1-78-0 / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / nightly / --all-features / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / nightly / --all-features / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / --no-default-features / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / --no-default-features / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy-derive / nightly / / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy-derive / nightly / / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / stable / / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / stable / / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / nightly / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / no-zerocopy-core-error-1-81-0 / / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-core-error-1-81-0 / / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-core-error-1-81-0 / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build (zerocopy / nightly / --simd / aarch64_be-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build (zerocopy / nightly / --simd / aarch64_be-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / nightly / --no-default-features / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / nightly / --no-default-features / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-generic-bounds-in-const-fn-1-61-0 / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Generate code coverage
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / msrv / --no-default-features / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Generate code coverage
The operation was canceled.
|
|
Build & Test (zerocopy / msrv / --no-default-features / x86_64-pc-windows-msvc)
The operation was canceled.
|
|
Build & Test (zerocopy / nightly / --no-default-features / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / nightly / --no-default-features / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / --no-default-features / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / --no-default-features / x86_64-pc-windows-msvc)
The operation was canceled.
|
|
Build & Test (zerocopy / nightly / --all-features / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / nightly / --all-features / x86_64-pc-windows-msvc)
The operation was canceled.
|
|
Build & Test (zerocopy-derive / nightly / / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy-derive / nightly / / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy-derive / msrv / / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy-derive / msrv / / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-generic-bounds-in-const-fn-1-61-0 / / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-generic-bounds-in-const-fn-1-61-0 / / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build (zerocopy / nightly / --simd / avr-none)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / stable / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Check GitHub Actions
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build (zerocopy / nightly / --simd / avr-none)
The operation was canceled.
|
|
|
|
Check GitHub Actions
The operation was canceled.
|
|
Build & Test (zerocopy / nightly / / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / msrv / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / msrv / --features __internal_use_only_features_that_work_on_stable / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / nightly / / i686-unknown-linux-gnu)
The operation was canceled.
|
|
|
|
|
|
Build & Test (zerocopy / nightly / --all-features / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / nightly / --all-features / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / nightly / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Run codegen tests
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Run codegen tests
The operation was canceled.
|
|
Run tests under Kani
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-core-error-1-81-0 / --no-default-features / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Run tests under Kani
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-core-error-1-81-0 / --no-default-features / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / msrv / / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / stable / --no-default-features / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / stable / --no-default-features / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / msrv / / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / stable / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / msrv / / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / msrv / / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / --no-default-features / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / / x86_64-pc-windows-msvc)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / --no-default-features / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / --no-default-features / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy-derive / msrv / / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy-derive / msrv / / x86_64-pc-windows-msvc)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-diagnostic-on-unimplemented-1-78-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / --no-default-features / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / --no-default-features / x86_64-pc-windows-msvc)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / no-zerocopy-generic-bounds-in-const-fn-1-61-0 / --no-default-features / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy-derive / nightly / / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy-derive / nightly / / x86_64-pc-windows-msvc)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / --no-default-features / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / --no-default-features / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / msrv / --no-default-features / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / msrv / --no-default-features / i686-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / --no-default-features / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / / x86_64-pc-windows-msvc)
The operation was canceled.
|
|
Build & Test (zerocopy / msrv / / x86_64-pc-windows-msvc)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / msrv / / x86_64-pc-windows-msvc)
The operation was canceled.
|
|
Build & Test (zerocopy / msrv / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / / x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
|
|
Build & Tests
Canceling since a higher priority waiting request for Build & Tests-refs/pull/3117/merge exists
|
|
Check stale stderr files
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Check crate versions match
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Check MSRV is minimal
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Check Rust formatting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Check README.md
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / nightly / / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy-derive / stable / / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / stable / --no-default-features / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-diagnostic-on-unimplemented-1-78-0 / --no-default-features / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-diagnostic-on-unimplemented-1-78-0 / / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / stable / / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / msrv / --no-default-features / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy-derive / stable / / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-generic-bounds-in-const-fn-1-61-0 / --no-default-features / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / stable / --features __internal_use_only_features_that_work_on_stable / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy-derive / msrv / / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-generic-bounds-in-const-fn-1-61-0 / / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / nightly / / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / nightly / --features __internal_use_only_features_that_work_on_stable / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / stable / / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / stable / --no-default-features / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-core-error-1-81-0 / --no-default-features / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / --no-default-features / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-core-error-1-81-0 / / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-diagnostic-on-unimplemented-1-78-0 / / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-generic-bounds-in-const-fn-1-61-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / nightly / --no-default-features / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy-derive / stable / / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-core-error-1-81-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-diagnostic-on-unimplemented-1-78-0 / --no-default-features / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-diagnostic-on-unimplemented-1-78-0 / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / nightly / --all-features / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / --no-default-features / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy-derive / nightly / / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / stable / / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / nightly / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-core-error-1-81-0 / / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-core-error-1-81-0 / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build (zerocopy / nightly / --simd / aarch64_be-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / nightly / --no-default-features / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-generic-bounds-in-const-fn-1-61-0 / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Generate code coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / msrv / --no-default-features / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / nightly / --no-default-features / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / --no-default-features / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / nightly / --all-features / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy-derive / nightly / / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy-derive / msrv / / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-generic-bounds-in-const-fn-1-61-0 / / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build (zerocopy / nightly / --simd / avr-none)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / stable / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Check GitHub Actions
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / nightly / / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / msrv / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / msrv / --features __internal_use_only_features_that_work_on_stable / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / nightly / --all-features / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / nightly / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Run codegen tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-core-error-1-81-0 / --no-default-features / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / stable / --no-default-features / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / msrv / / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / stable / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / msrv / / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / --no-default-features / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / --no-default-features / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-simd-x86-avx12-1-89-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / --no-default-features / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy-derive / msrv / / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-diagnostic-on-unimplemented-1-78-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / --no-default-features / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-generic-bounds-in-const-fn-1-61-0 / --no-default-features / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy-derive / nightly / / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / --no-default-features / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / msrv / --no-default-features / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / --no-default-features / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / msrv / / x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / msrv / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 / --features __internal_use_only_features_that_work_on_stable / i686-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build & Test (zerocopy / no-zerocopy-target-has-atomics-1-60-0 / --features __internal_use_only_features_that_work_on_stable / x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|