deps: bump hkdf from 0.12.4 to 0.13.0 #19836
dependabot[bot]ci.yml
on: pull_request
gather_published_crates
15s
Run all WASM tests
1m 21s
Compile with MSRV
27s
Check rustdoc intra-doc links
32s
IPFS Integration tests
23s
examples
31s
semver
25m 20s
rustfmt
16s
manifest_lint
17s
Check for changes in proto files
20s
Ensure that `Cargo.lock` is up-to-date
16s
cargo-deny
29s
Matrix: clippy
Matrix: cross
Matrix: feature_matrix
Matrix: test
Annotations
296 errors and 58 warnings
|
Compile with select features (mdns tcp dns tokio)
Process completed with exit code 101.
|
|
Compile with select features (mdns tcp dns tokio):
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Compile with select features (mdns tcp dns tokio):
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Compile with select features (mdns tcp dns tokio):
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Compile with select features (mdns tcp dns tokio):
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Compile with select features (mdns tcp dns tokio):
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
IPFS Integration tests
Process completed with exit code 101.
|
|
IPFS Integration tests:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
IPFS Integration tests:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
IPFS Integration tests:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
IPFS Integration tests:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
IPFS Integration tests:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Compile with MSRV
Process completed with exit code 101.
|
|
Compile with MSRV:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Compile with MSRV:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Compile with MSRV:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Compile with MSRV:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Compile with MSRV:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Check rustdoc intra-doc links
Process completed with exit code 101.
|
|
Check rustdoc intra-doc links:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Check rustdoc intra-doc links:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Check rustdoc intra-doc links:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Check rustdoc intra-doc links:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Check rustdoc intra-doc links:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Compile on x86_64-apple-darwin
Process completed with exit code 101.
|
|
Compile on x86_64-apple-darwin:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Compile on x86_64-apple-darwin:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Compile on x86_64-apple-darwin:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Compile on x86_64-apple-darwin:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Compile on x86_64-apple-darwin:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Compile on wasm32-wasip1
The strategy configuration was canceled because "cross.x86_64-apple-darwin_macos" failed
|
|
clippy (1.93.1)
Process completed with exit code 101.
|
|
clippy (1.93.1):
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
clippy (1.93.1):
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
clippy (1.93.1):
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
clippy (1.93.1):
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
clippy (1.93.1):
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Compile on wasm32-unknown-emscripten
The strategy configuration was canceled because "cross.x86_64-apple-darwin_macos" failed
|
|
Compile on wasm32-unknown-emscripten
A task was canceled.
|
|
Compile on x86_64-pc-windows-msvc
The strategy configuration was canceled because "cross.x86_64-apple-darwin_macos" failed
|
|
Compile on x86_64-pc-windows-msvc
The operation was canceled.
|
|
Compile on wasm32-unknown-unknown
The strategy configuration was canceled because "cross.x86_64-apple-darwin_macos" failed
|
|
Compile on wasm32-unknown-unknown
The operation was canceled.
|
|
Run all WASM tests
Process completed with exit code 1.
|
|
examples
Process completed with exit code 101.
|
|
examples:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
examples:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
examples:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
examples:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
examples:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
clippy (beta)
Process completed with exit code 101.
|
|
clippy (beta):
identity/src/keypair.rs#L368
the associated function or constant `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
clippy (beta):
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
clippy (beta):
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
clippy (beta):
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
clippy (beta):
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-plaintext
Process completed with exit code 101.
|
|
Test libp2p-plaintext:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-plaintext:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-plaintext:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-plaintext:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-plaintext:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-core
Process completed with exit code 101.
|
|
Test libp2p-core:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-core:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-core:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-core:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-core:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-noise
Process completed with exit code 101.
|
|
Test libp2p-noise:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-noise:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-noise:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-noise:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-noise:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-identify
Process completed with exit code 101.
|
|
Test libp2p-identify:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-identify:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-identify:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-identify:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-identify:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-ping
Process completed with exit code 101.
|
|
Test libp2p-ping:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-ping:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-ping:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-ping:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-ping:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p
Process completed with exit code 101.
|
|
Test libp2p:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-websocket-websys
Process completed with exit code 101.
|
|
Test libp2p-websocket-websys:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-websocket-websys:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-websocket-websys:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-websocket-websys:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-websocket-websys:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-webtransport-websys
Process completed with exit code 101.
|
|
Test libp2p-webtransport-websys:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-webtransport-websys:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-webtransport-websys:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-webtransport-websys:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-webtransport-websys:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-swarm
Process completed with exit code 101.
|
|
Test libp2p-swarm:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-swarm:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-swarm:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-swarm:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-swarm:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-request-response
Process completed with exit code 101.
|
|
Test libp2p-request-response:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-request-response:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-request-response:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-request-response:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-request-response:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-relay
Process completed with exit code 101.
|
|
Test libp2p-relay:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-relay:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-relay:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-relay:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-relay:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-autonat
Process completed with exit code 101.
|
|
Test libp2p-autonat:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-autonat:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-autonat:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-autonat:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-autonat:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-connection-limits
Process completed with exit code 101.
|
|
Test libp2p-connection-limits:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-connection-limits:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-connection-limits:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-connection-limits:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-connection-limits:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-allow-block-list
Process completed with exit code 101.
|
|
Test libp2p-allow-block-list:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-allow-block-list:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-allow-block-list:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-allow-block-list:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-allow-block-list:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-identity
Process completed with exit code 101.
|
|
Test libp2p-identity:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-identity:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-identity:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-identity:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-identity:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-gossipsub
Process completed with exit code 101.
|
|
Test libp2p-gossipsub:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-gossipsub:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-gossipsub:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-gossipsub:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-gossipsub:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-webrtc-utils
Process completed with exit code 101.
|
|
Test libp2p-webrtc-utils:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-webrtc-utils:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-webrtc-utils:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-webrtc-utils:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-webrtc-utils:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-tls
Process completed with exit code 101.
|
|
Test libp2p-tls:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-tls:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-tls:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-tls:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-tls:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-mplex
Process completed with exit code 101.
|
|
Test libp2p-mplex:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-mplex:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-mplex:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-mplex:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-mplex:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-webrtc
Process completed with exit code 101.
|
|
Test libp2p-webrtc:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-webrtc:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-webrtc:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-webrtc:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-webrtc:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-dcutr
Process completed with exit code 101.
|
|
Test libp2p-dcutr:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-dcutr:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-dcutr:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-dcutr:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-dcutr:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-websocket
Process completed with exit code 101.
|
|
Test libp2p-websocket:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-websocket:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-websocket:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-websocket:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-websocket:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-server
Process completed with exit code 101.
|
|
Test libp2p-server:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-server:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-server:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-server:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-server:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-floodsub
Process completed with exit code 101.
|
|
Test libp2p-floodsub:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-floodsub:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-floodsub:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-floodsub:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-floodsub:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-quic
Process completed with exit code 101.
|
|
Test libp2p-quic:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-quic:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-quic:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-quic:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-quic:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-kad
Process completed with exit code 101.
|
|
Test libp2p-kad:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-kad:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-kad:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-kad:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-kad:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-memory-connection-limits
Process completed with exit code 101.
|
|
Test libp2p-memory-connection-limits:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-memory-connection-limits:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-memory-connection-limits:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-memory-connection-limits:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-memory-connection-limits:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-swarm-test
Process completed with exit code 101.
|
|
Test libp2p-swarm-test:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-swarm-test:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-swarm-test:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-swarm-test:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-swarm-test:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-metrics
Process completed with exit code 101.
|
|
Test libp2p-metrics:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-metrics:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-metrics:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-metrics:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-metrics:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-uds
Process completed with exit code 101.
|
|
Test libp2p-uds:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-uds:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-uds:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-uds:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-uds:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-stream
Process completed with exit code 101.
|
|
Test libp2p-stream:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-stream:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-stream:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-stream:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-stream:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-pnet
Process completed with exit code 101.
|
|
Test libp2p-pnet:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-pnet:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-pnet:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-pnet:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-pnet:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-perf
Process completed with exit code 101.
|
|
Test libp2p-perf:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-perf:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-perf:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-perf:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-perf:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-webrtc-websys
Process completed with exit code 101.
|
|
Test libp2p-webrtc-websys:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-webrtc-websys:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-webrtc-websys:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-webrtc-websys:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-webrtc-websys:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-yamux
Process completed with exit code 101.
|
|
Test libp2p-yamux:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-yamux:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-yamux:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-yamux:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-yamux:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-upnp
Process completed with exit code 101.
|
|
Test libp2p-upnp:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-upnp:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-upnp:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-upnp:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-upnp:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-rendezvous
Process completed with exit code 101.
|
|
Test libp2p-rendezvous:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-rendezvous:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-rendezvous:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-rendezvous:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-rendezvous:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-mdns
Process completed with exit code 101.
|
|
Test libp2p-mdns:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-mdns:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-mdns:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-mdns:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-mdns:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-tcp
Process completed with exit code 101.
|
|
Test libp2p-tcp:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-tcp:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-tcp:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-tcp:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-tcp:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Test libp2p-dns
Process completed with exit code 101.
|
|
Test libp2p-dns:
identity/src/keypair.rs#L368
the function or associated item `new` exists for struct `GenericHkdf<Hmac<CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>>>`, but its trait bounds were not satisfied
|
|
Test libp2p-dns:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: HashMarker` is not satisfied
|
|
Test libp2p-dns:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: FixedOutput` is not satisfied
|
|
Test libp2p-dns:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<..., ..., ...>>: BlockSizeUser` is not satisfied
|
|
Test libp2p-dns:
identity/src/keypair.rs#L368
the trait bound `CoreWrapper<CtVariableCoreWrapper<Sha256VarCore, ..., ...>>: CoreProxy` is not satisfied
|
|
Compile with select features (mdns tcp dns tokio)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
IPFS Integration tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Compile with MSRV
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Check rustdoc intra-doc links
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Compile on x86_64-apple-darwin
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
clippy (1.93.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Compile on 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: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run all WASM tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
examples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
clippy (beta)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Check for changes in proto files
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5, tj-actions/glob@v22. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
rustfmt
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
manifest_lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Ensure that `Cargo.lock` is up-to-date
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test quick-protobuf-codec
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-plaintext
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-core
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-noise
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-identify
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-ping
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-websocket-websys
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-webtransport-websys
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-swarm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-request-response
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-relay
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-autonat
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-connection-limits
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-allow-block-list
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-identity
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-gossipsub
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-swarm-derive
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test rw-stream-sink
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-webrtc-utils
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-tls
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-mplex
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-webrtc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-dcutr
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-websocket
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-server
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-floodsub
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test multistream-select
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-quic
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-kad
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-memory-connection-limits
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-swarm-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-metrics
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-uds
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-stream
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-pnet
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-perf
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-webrtc-websys
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-yamux
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-upnp
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-rendezvous
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-mdns
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-tcp
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test libp2p-dns
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|