Skip to content
This repository was archived by the owner on Apr 27, 2026. It is now read-only.

Bump cryptography from 42.0.4 to 46.0.6 #2269

Bump cryptography from 42.0.4 to 46.0.6

Bump cryptography from 42.0.4 to 46.0.6 #2269

Triggered via pull request March 28, 2026 12:41
Status Cancelled
Total duration 9m 44s
Artifacts

unittests.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 4 warnings
python 3.9, bitcoind 28.3 on macos-13
The configuration 'macos-13-us-default' is not supported
python 3.13, bitcoind 29.2 on macos-13
The configuration 'macos-13-us-default' is not supported
python 3.13, bitcoind 28.3 on macos-13
The configuration 'macos-13-us-default' is not supported
python 3.9, bitcoind 29.2 on macos-13
The configuration 'macos-13-us-default' is not supported
python 3.13, bitcoind 29.2 on ubuntu-latest
Process completed with exit code 1.
python 3.13, bitcoind 28.3 on ubuntu-latest
Process completed with exit code 1.
python 3.9, bitcoind 29.2 on ubuntu-latest
Process completed with exit code 1.
python 3.9, bitcoind 28.3 on ubuntu-latest
Process completed with exit code 1.
python 3.13, bitcoind 29.2 on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@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/
python 3.13, bitcoind 28.3 on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@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/
python 3.9, bitcoind 29.2 on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@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/
python 3.9, bitcoind 28.3 on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@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/