Allow cancellation of pending splice funding negotiations #23071
build.yml
on: pull_request
fuzz
1h 15m
Matrix: build-bindings / build
Matrix: build-cfg-flags / build
Matrix: build-features / build
Matrix: build-nostd / build
Matrix: build-sync / build
Matrix: build-workspace / build
ext-test
7m 1s
benchmark
15m 24s
check_release
2m 50s
check_docs
10m 9s
fuzz_sanity
14m 21s
linting
2m 33s
rustfmt
13s
tor-connect
5m 45s
notify-failure
0s
Annotations
14 warnings
|
rustfmt
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
linting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
check_release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
tor-connect
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
benchmark
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/checkout@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/
|
|
check_docs
Runner Version 2.331.0 will no longer be able to run jobs on April 29, 2026, please update your runner version.
|
|
build-cfg-flags / build (self-hosted, 1.75.0)
Runner Version 2.331.0 will no longer be able to run jobs on April 29, 2026, please update your runner version.
|
|
ext-test
Runner Version 2.331.0 will no longer be able to run jobs on April 29, 2026, please update your runner version.
|
|
build-workspace / build (self-hosted, 1.75.0)
Runner Version 2.331.0 will no longer be able to run jobs on April 29, 2026, please update your runner version.
|
|
fuzz_sanity
Runner Version 2.331.0 will no longer be able to run jobs on April 29, 2026, please update your runner version.
|
|
build-sync / build (self-hosted, 1.75.0)
Runner Version 2.331.0 will no longer be able to run jobs on April 29, 2026, please update your runner version.
|
|
build-bindings / build (self-hosted, 1.75.0)
Runner Version 2.331.0 will no longer be able to run jobs on April 29, 2026, please update your runner version.
|
|
fuzz
Runner Version 2.331.0 will no longer be able to run jobs on April 29, 2026, please update your runner version.
|
|
coverage
Runner Version 2.331.0 will no longer be able to run jobs on April 29, 2026, please update your runner version.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
hfuzz-corpus
|
36.5 MB |
sha256:794d0abc267d8deb1913ba900be378a1e97155a49683f7849f452ed93cb9f949
|
|