Skip to content

Fixed python & feature test failures caused by Werkzeug 3.1.7 rejecting empty Host header in CSRF token generation. #5293

Fixed python & feature test failures caused by Werkzeug 3.1.7 rejecting empty Host header in CSRF token generation.

Fixed python & feature test failures caused by Werkzeug 3.1.7 rejecting empty Host header in CSRF token generation. #5293

Triggered via pull request March 26, 2026 11:45
Status Success
Total duration 28m 27s
Artifacts 30

run-python-tests-pg.yml

on: pull_request
Matrix: run-python-tests-pg
Fit to window
Zoom out
Zoom in

Annotations

16 warnings
run-python-tests-pg (macos-latest, 17)
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/setup-python@v5, actions/upload-artifact@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/
run-python-tests-pg (ubuntu-22.04, 16)
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/setup-python@v5, actions/upload-artifact@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/
run-python-tests-pg (macos-latest, 16)
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/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-python-tests-pg (macos-latest, 14)
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/setup-python@v5, actions/upload-artifact@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/
run-python-tests-pg (macos-latest, 14)
postgresql@14 has been deprecated because it is not supported upstream! It will be disabled on 2026-11-12.
run-python-tests-pg (ubuntu-22.04, 17)
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/setup-python@v5, actions/upload-artifact@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/
run-python-tests-pg (macos-latest, 18)
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/setup-python@v5, actions/upload-artifact@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/
run-python-tests-pg (macos-latest, 15)
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/setup-python@v5, actions/upload-artifact@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/
run-python-tests-pg (ubuntu-22.04, 15)
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/setup-python@v5, actions/upload-artifact@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/
run-python-tests-pg (ubuntu-22.04, 18)
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/setup-python@v5, actions/upload-artifact@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/
run-python-tests-pg (ubuntu-22.04, 14)
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/setup-python@v5, actions/upload-artifact@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/
run-python-tests-pg (windows-latest, 14)
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/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-python-tests-pg (windows-latest, 17)
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/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-python-tests-pg (windows-latest, 16)
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/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-python-tests-pg (windows-latest, 15)
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/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run-python-tests-pg (windows-latest, 18)
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/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
regression-log-macos-latest-pg14
1.01 MB
sha256:3f1b54873a1a26d138b86be98cca4ffa17e9a8acb449b0330d39419ef1d9d98a
regression-log-macos-latest-pg15
1.02 MB
sha256:d12b1c4ae1afff11498d4b6f0626f84c0b24a879862620730203e9828bc101e4
regression-log-macos-latest-pg16
1.02 MB
sha256:4de79e5c3f8b53a4552b7638329bad3001d8e9f738544abfe8d6778bed786d0e
regression-log-macos-latest-pg17
1.02 MB
sha256:2f72f17b2b1174589478c880d0e6457beed2b665bc2d3a300a855a8c99fdd0e1
regression-log-macos-latest-pg18
1.02 MB
sha256:8cd5f594eacfa99b41c6d61d54c4b82824f9dd0dfa2d3c6851ea8f05dce43fac
regression-log-ubuntu-22.04-pg14
1.06 MB
sha256:125b2f6a698d054ff39b048064b9d5cd79011b2e35ce25679576b90144a4b39b
regression-log-ubuntu-22.04-pg15
1.07 MB
sha256:b9ff521ead9dbe506f1e7c1276fb0f6cf34edf0654358bfecfe85428de647504
regression-log-ubuntu-22.04-pg16
1.07 MB
sha256:242968dff6cb92bc3998200a88933e0e15d3ed91471b19731d26d7331041c289
regression-log-ubuntu-22.04-pg17
1.07 MB
sha256:a6c6f1c7ef8ddfa4e62503c9a5f2657332bfb48820d5462123db7ca24753a585
regression-log-ubuntu-22.04-pg18
1.06 MB
sha256:63faa5c6c7ddeef86db2342a0d881cc293f84239b7f137f20c68929b440feadd
regression-log-windows-latest-pg14
1.07 MB
sha256:1bc04826bb7342122ccc78178dab2e0f29b0564118709a1fdb687cfbb07e23ca
regression-log-windows-latest-pg15
1.08 MB
sha256:b7b317c5be280422b98f8664a014172c6896f6572d57abc1ade2eaa7d2a716fa
regression-log-windows-latest-pg16
1.08 MB
sha256:7491d8fef30d1be0b20ff2171b72327e94277ccea446a08584c799594661beb8
regression-log-windows-latest-pg17
1.08 MB
sha256:ab238796b688bd51ee697c7091c0fc8bce619084541d707f5e4f697aa997b129
regression-log-windows-latest-pg18
1.08 MB
sha256:a3028001e04682668262eedb1d29705e22e70d6e21aec75361c70b91d21a3d7c
server-log-macos-latest-pg14
359 KB
sha256:97262302500c806fac6feba71d22d55613f90a4387433a5768cc00d92d6ed932
server-log-macos-latest-pg15
371 KB
sha256:04bb8e7a07652e65eb278fc701af4934a7e3eeeb90d3a59f1c1fc9e86d3ed505
server-log-macos-latest-pg16
364 KB
sha256:c2007b18229d82fea55e74e241857a71a9afc6185f260d4622467560116a4d6c
server-log-macos-latest-pg17
365 KB
sha256:ba2ed623ae61ab3dbd6a46800db1f8e22c68773dca0377169eb9f2888e140b18
server-log-macos-latest-pg18
368 KB
sha256:a40d2fb7ba86830a68ff2bfb069af95be01e76f95b317b36437f8e53629e5578
server-log-ubuntu-22.04-pg14
388 KB
sha256:a445dcf0320e61b2a6e7932065e209b5c99f1286d05699f52c79482080ace986
server-log-ubuntu-22.04-pg15
402 KB
sha256:bf576957b119031869b17adac1c45b90d7a5334dd0b046c95011ce4dd4c234c6
server-log-ubuntu-22.04-pg16
403 KB
sha256:f5f32275b5871b959627acc350023f6ddc616b2bcb3742059d0bdb85f74cf598
server-log-ubuntu-22.04-pg17
401 KB
sha256:547bdd1bc106d9be459d8b7e303565c156e6133b8af9d68123ba40e809e38037
server-log-ubuntu-22.04-pg18
402 KB
sha256:dee860b3adf793ac9dd4d020c95f9c3a144b929d77d471b84d089f861d7fd332
server-log-windows-latest-pg14
597 KB
sha256:7ce3da6ac62696a97caa7f8884809eed2dc71e6336e8b50017f6b3dfc5fdf129
server-log-windows-latest-pg15
599 KB
sha256:e6319dcb0ee53841220812c54a3b79a9cf949d6bd1ca6bcb49ced3f984e1cd79
server-log-windows-latest-pg16
600 KB
sha256:38283701a832514c8a4a3c3e4b0f4a212d1fcbf20b5bb60c6fc09e86409c9d9d
server-log-windows-latest-pg17
597 KB
sha256:e08c3fab260e20afd8cb8736e9b8a6d792322324108397dad37392da7dd60af6
server-log-windows-latest-pg18
592 KB
sha256:d7f91f4ec7757098727f70173c9e63f0bed997140e6a970c5e10aa068ca41f68