fix(upnp): panic with "mapping should exist" #20103
ci.yml
on: pull_request
gather_published_crates
17s
Run all WASM tests
1m 1s
Compile with MSRV
40s
Check rustdoc intra-doc links
1m 0s
IPFS Integration tests
58s
examples
1m 1s
semver
48s
rustfmt
14s
manifest_lint
14s
Check for changes in proto files
28s
Ensure that `Cargo.lock` is up-to-date
21s
cargo-deny
29s
Matrix: clippy
Matrix: cross
Matrix: feature_matrix
Matrix: test
Annotations
74 errors, 29 warnings, and 1 notice
|
rustfmt
Process completed with exit code 1.
|
|
Test prost-codec
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test multistream-select
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-identify
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-swarm-derive
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-mplex
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-swarm
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-noise
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-core
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-request-response
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-yamux
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-connection-limits
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-gossipsub
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-dns
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-tls
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-autonat
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-swarm-test
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-metrics
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-relay
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-websocket
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-dcutr
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-memory-connection-limits
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-identity
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-quic
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-floodsub
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-webrtc-utils
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-mdns
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-upnp
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-uds
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-webrtc-websys
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-webrtc
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-websocket-websys
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-stream
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Compile on x86_64-apple-darwin
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
semver
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
semver
The operation was canceled.
|
|
Test libp2p-webtransport-websys
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-webtransport-websys
The operation was canceled.
|
|
Test libp2p-pnet
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-pnet
The operation was canceled.
|
|
clippy (1.93.1)
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
clippy (1.93.1)
The operation was canceled.
|
|
Test rw-stream-sink
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test rw-stream-sink
The operation was canceled.
|
|
Compile on x86_64-pc-windows-msvc
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Compile on x86_64-pc-windows-msvc
The operation was canceled.
|
|
IPFS Integration tests
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
IPFS Integration tests
The operation was canceled.
|
|
Test libp2p-plaintext
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-plaintext
The operation was canceled.
|
|
Test libp2p-rendezvous
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-rendezvous
The operation was canceled.
|
|
Check rustdoc intra-doc links
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Check rustdoc intra-doc links
The operation was canceled.
|
|
Run all WASM tests
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Run all WASM tests
The operation was canceled.
|
|
Test libp2p-kad
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-kad
The operation was canceled.
|
|
examples
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
examples
The operation was canceled.
|
|
Test libp2p-allow-block-list
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-allow-block-list
The operation was canceled.
|
|
Test libp2p-tcp
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-tcp
The operation was canceled.
|
|
Test libp2p-server
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-server
The operation was canceled.
|
|
Test libp2p-ping
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-ping
The operation was canceled.
|
|
Test libp2p-perf
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
Test libp2p-perf
The operation was canceled.
|
|
Continuous integration
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
clippy (beta)
Canceling since a higher priority waiting request for Continuous integration-refs/pull/6459/merge exists
|
|
clippy (beta)
The operation was canceled.
|
|
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 16th, 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 16th, 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 wasm32-unknown-emscripten
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 16th, 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 wasm32-unknown-unknown
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 16th, 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 16th, 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 wasm32-wasip1
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 16th, 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 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 16th, 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. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 16th, 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 16th, 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/
|
|
semver
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 16th, 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. Actions will be forced to run with Node.js 24 by default starting June 16th, 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. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 16th, 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: r7kamura/rust-problem-matchers@9fe7ca9f6550e5d6358e179d451cc25ea6b54f98, Swatinem/rust-cache@779680da715d629ac1d338a641029a2f4372abb5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 16th, 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 16th, 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 16th, 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. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 16th, 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 16th, 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 16th, 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 16th, 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 16th, 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 16th, 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 16th, 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 16th, 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 16th, 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 16th, 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
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|