Skip to content

fix: repo-wide correctness, security & filesystem-safety hardening pass (v3.2.0) #242

fix: repo-wide correctness, security & filesystem-safety hardening pass (v3.2.0)

fix: repo-wide correctness, security & filesystem-safety hardening pass (v3.2.0) #242

Triggered via pull request May 29, 2026 13:17
Status Failure
Total duration 12m 44s
Artifacts 47

ci.yml

on: pull_request
Matrix: coverage-docker
Matrix: test
Matrix: e2e-docker
Matrix: e2e
coverage-merge
19s
coverage-merge
Fit to window
Zoom out
Zoom in

Annotations

1 error, 17 warnings, and 1 notice
test (windows-latest)
Process completed with exit code 1.
dispatch-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065. 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
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. 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/
coverage-docker (cargo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
coverage-docker (golang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
coverage-docker (npm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
coverage-docker (nuget)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
coverage-docker (deno)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
coverage-docker (gem)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
coverage-docker (pypi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
coverage-docker (composer)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
coverage-docker (maven)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
coverage-merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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 (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. 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 (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. 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 (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. 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-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. 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 (windows-latest)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

Artifacts

Produced during runtime
Name Size Digest
SocketDev~socket-patch~0X3Q0B.dockerbuild
17.3 KB
sha256:44632c4faa8a1c5fdbaa629ad1dfa3f1408a2a8a586a2729cc2d4a6ade552f62
SocketDev~socket-patch~1230ZK.dockerbuild
33.2 KB
sha256:e3b4d1468555a22e44a2d0ceebf54a5ee010b524b89c0c123303906343d94c7b
SocketDev~socket-patch~2IWGBC.dockerbuild
33.2 KB
sha256:5c35db9660abecb088d01d7054015d047eab5357569f43832de4fc0831137da1
SocketDev~socket-patch~2NDP9I.dockerbuild
16.2 KB
sha256:3b5aa1da4959f56df86af400a89aa473209a0e272c965e927293e13a10f5de49
SocketDev~socket-patch~5FQKLX.dockerbuild
34.1 KB
sha256:c5832e81e8fdbe2f55496d54c3ff4d8cfc2d38c3f72ccfc81a8b28497ef83597
SocketDev~socket-patch~5S6UXP.dockerbuild
33.2 KB
sha256:43609da094d790cfa79e4f2182a0832c7fe88691244ddb6476e92469abd2d2ce
SocketDev~socket-patch~6BE30I.dockerbuild
11.8 KB
sha256:3bea41db76b70e40b66374a5043d5ebc5a12cf4520fcc351e1357a202ecbd54e
SocketDev~socket-patch~7DD6TX.dockerbuild
33.2 KB
sha256:35b8bdcfa8308841c8a741a131aa8bfade810a81b7570239482461fab6f140a8
SocketDev~socket-patch~AZZMMX.dockerbuild
34 KB
sha256:8811a8f4c6ee01d624c17c446ec2c15b80f385c8f3cb7dcaad313cee60565c28
SocketDev~socket-patch~EGPQPG.dockerbuild
20.8 KB
sha256:8b375756abdac0e878fad7411bff5f91bb9155116b27b9aa0bf0e92ada54ed30
SocketDev~socket-patch~F0E1D2.dockerbuild
33.7 KB
sha256:862621cad7feb301013af41b393c74b1afc65e7305abaed790f7cf9eb6c78041
SocketDev~socket-patch~G0OBYZ.dockerbuild
20.7 KB
sha256:ecc7eeb86a240a837988bcb8d608640afc339edae44e3db011970a89ac09db64
SocketDev~socket-patch~H2MUYG.dockerbuild
16 KB
sha256:af7056c4a31ada4a4aa4c59432d8fc6160e4fa10e2cb95c19106a291b0313083
SocketDev~socket-patch~J40OO0.dockerbuild
32.9 KB
sha256:07a1f49a36a77f7c4b73c9d27b200135cf9ae563d0d09d5d349ac48af2f97d70
SocketDev~socket-patch~JYDT1B.dockerbuild
20.5 KB
sha256:bd9ac01c42b08b73b97056e268940cd9f74ed30f3d5fba8c65cfda1e21e73695
SocketDev~socket-patch~K09K8P.dockerbuild
33.5 KB
sha256:36b8cde68374a6042005c70b9b8bd8cd9d95fd59fbef3245b2496c39ee41e0f4
SocketDev~socket-patch~LK194G.dockerbuild
32.9 KB
sha256:8f3f77eb175550edf2bd9181900b2e4aa52a1357bf63998ac2961074b0b7891c
SocketDev~socket-patch~LOSWA8.dockerbuild
19.9 KB
sha256:2fc799a56005786d181df13b4ea141b25931c363f8ab5cf0f3356e15e9d9266f
SocketDev~socket-patch~N3NM3M.dockerbuild
34.1 KB
sha256:1b828ca318344a0a8fe3cd3b896cbf3c3204811da45af4f32c1038cbe028b6d3
SocketDev~socket-patch~O06GOP.dockerbuild
33.6 KB
sha256:c032984af45c251bc8ae9a9a22fb342213a92bec88390edb4307761eb2ad5e45
SocketDev~socket-patch~O85FKM.dockerbuild
23.4 KB
sha256:ec72b581abaf4102f4052947e9ccb29219c6fe02c3fc44a46be1c03491eb03c4
SocketDev~socket-patch~OC4TH5.dockerbuild
21.5 KB
sha256:50038b390a5535b478e1663d493c92099073a2948521a41cf93d24d66c3ff1f4
SocketDev~socket-patch~OUDQQV.dockerbuild
33.7 KB
sha256:299ed283839af171cdf98c9e019bd8ac9335ea2a01aa717de07c417f9bcd89e3
SocketDev~socket-patch~PEP8MU.dockerbuild
33.2 KB
sha256:da9cf296abae1d3fe5a96268e5fe3a6776267b2c6e6e42f602cf1a900f9386b0
SocketDev~socket-patch~R7BBYZ.dockerbuild
20 KB
sha256:80ad5ca4086f74be1608fc6934c16d24ecb855b2b0949ee350a70ed45c252cec
SocketDev~socket-patch~RTAGPR.dockerbuild
33.2 KB
sha256:76ee09b40eea69fc353985ea2bbc3bbd77cd195654257f871dbf27013d07c0e1
SocketDev~socket-patch~S29WLW.dockerbuild
11.1 KB
sha256:70701884b249f2285b04cd58a3ffb8cdf9b24049a018406e21d35655b08f6fd3
SocketDev~socket-patch~WG56XC.dockerbuild
20.1 KB
sha256:7b5aa84e93aaf36179dc4cad8e48e894b6bac2d6884e0017945c459dfb8cca0b
SocketDev~socket-patch~WYI3QG.dockerbuild
33.9 KB
sha256:e1726bb2c3c0d4b22f908f2b85291b3ce2df24d09cf677c8dcf9edb11d498fa7
SocketDev~socket-patch~WYWC27.dockerbuild
16.5 KB
sha256:40f005301b793ae7fc7ee1355718e2bf08ccfa469a7af07d2880a98288b154e8
SocketDev~socket-patch~XB7CJP.dockerbuild
18.3 KB
sha256:8defbab7907cf2a0fcffd04a3b145b1ff0a1dd4ed44a2f7acc2f6414215667ae
SocketDev~socket-patch~XN6LYJ.dockerbuild
19.2 KB
sha256:4d2d126b0c7b4da3888c6697295431d62709fa6c45c403dfaebab4df7fb99efe
SocketDev~socket-patch~XVXU12.dockerbuild
33.3 KB
sha256:da3edac4d0bc3a1510c70ed50c0226d5250ded2bcc76650278d1120e9a9ecd46
SocketDev~socket-patch~XY37FX.dockerbuild
34.4 KB
sha256:5d8287fed9a9899b94a04a921c506fa9b037898065168cabb00e98853ee89091
SocketDev~socket-patch~Y4992Z.dockerbuild
24.2 KB
sha256:c6d43acc6cc7c7e96624387479290e4ffa0f4d97d5e885ae8337517e7ecc52b6
SocketDev~socket-patch~ZJIJKG.dockerbuild
21.7 KB
sha256:4454aa52abe0339e9f94ff04b88008fb445424f985198af40a3fa014c85b6ed2
coverage-docker-cargo Expired
34.7 KB
sha256:433d90cd54e19ee653cb8ce8464397ab5b2ef8921b6ceedab6b166c5a4a7faf4
coverage-docker-composer Expired
34.7 KB
sha256:6e0df723be5bdb71c903d66a32f37f9a03ccf39e553273162c143ea9bcb956d2
coverage-docker-deno Expired
34.7 KB
sha256:4b6301cea7539a1e262706086b1ba5c9fcbe976ad7b351a62db52654d8ae1034
coverage-docker-gem Expired
34.7 KB
sha256:2c8fae56f22be2343519513c03f54d739439228a55b22e1e6325baf1bd8a660e
coverage-docker-golang Expired
34.7 KB
sha256:077144f561f125342dd71258a5ab145212b86a3f2ffc12b460ccb5a4bd44868b
coverage-docker-maven Expired
34.7 KB
sha256:ed218d696881bd1cfcccef073109018073ad8b0c8e0da388bdc564a04d6506f8
coverage-docker-npm Expired
34.7 KB
sha256:6c09a98c5c97d8429b32ada03305bfb7b46a3dfa2b0f5400f8b7ad495febdcb4
coverage-docker-nuget Expired
34.7 KB
sha256:837abe2578644560c3b7bb66616ace8227c6fdeab02ea9ac692ea57918b6886a
coverage-docker-pypi Expired
34.7 KB
sha256:324c760de9957d19281475e991f9d45e348c6d935f52f16b01d5b2826e5f0d0a
coverage-host Expired
179 KB
sha256:3677be976d412744aa91f1476533e355e83ea5f1a35aadc841c5fb7a50ef3638
coverage-lcov Expired
182 KB
sha256:126dcd3f5f526111ce7bb543c5bb57634fbe6d73e67a3c0cb7e64fa5102c1e98