Skip to content

feat(vex): OpenVEX 0.2.0 attestation generator #215

feat(vex): OpenVEX 0.2.0 attestation generator

feat(vex): OpenVEX 0.2.0 attestation generator #215

Triggered via pull request May 24, 2026 21:41
Status Failure
Total duration 17m 36s
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

3 errors, 17 warnings, and 1 notice
test (macos-latest)
Process completed with exit code 101.
test (ubuntu-latest)
Process completed with exit code 101.
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 (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 (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 (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 (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 (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 (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 (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-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 (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/
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 (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/
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/
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/
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-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~02WMI9.dockerbuild
33.6 KB
sha256:5454a49edf0d6215e3bbbb7f917ab0be3fbed63037c8b767ada0c9d0d3e3b1bf
SocketDev~socket-patch~1BPDAP.dockerbuild
33.9 KB
sha256:2a59948f1398e8b144d41a97d186a6a34cce335bb51a9425f8826025e7002b31
SocketDev~socket-patch~1P4RUL.dockerbuild
20 KB
sha256:a92e5aabe6aa9ef1b26399baa8de5adeaa01c99d5d25400da5561a3363093201
SocketDev~socket-patch~2W6BAH.dockerbuild
20.8 KB
sha256:59c9d46e3e1f2ae40ccff4164774f47ad0bb463c2df5a95694c75670df90f3d3
SocketDev~socket-patch~39C4YL.dockerbuild
33.5 KB
sha256:05189a4e72c55b64230b3948cbc06e2c8baedaa1a8f9df3b1a7239f8549d204b
SocketDev~socket-patch~5DDO9P.dockerbuild
32.9 KB
sha256:0b0f1377419b3264f1ef158870ea6940d03cb93eeb8e65eef9104944af29ebdf
SocketDev~socket-patch~6SXB1G.dockerbuild
32.8 KB
sha256:ade9f3f37e9e778f62d2a589499a15df8e46222742f8e1349cfd261384aa3590
SocketDev~socket-patch~ALTICM.dockerbuild
20.7 KB
sha256:3a5e7581696f7a433511520892ab7c6d908f32536dc33397b371b89062edcbf0
SocketDev~socket-patch~BCXVE1.dockerbuild
33.4 KB
sha256:e2d329f9c1ec89520504089efb54382039b71062abac924cb33524aa1d57fa02
SocketDev~socket-patch~BGMW9T.dockerbuild
24 KB
sha256:a455125aac6cff8d65d5c179651198278db4edb13e1c49476a609168ad4c800e
SocketDev~socket-patch~C01Z6N.dockerbuild
16.9 KB
sha256:177a4d4cd4abbb517d80aacf83ea8d07a1a85f6b4917ae058665e4d7bf07634d
SocketDev~socket-patch~CUSJ1E.dockerbuild
32.9 KB
sha256:3491411bf00cb137beed1661c07a23b830206f357e99df694018c0b562bb76c7
SocketDev~socket-patch~GUU51E.dockerbuild
17.7 KB
sha256:87218440a636faf4054f91a35b86d53afd63072fca4d5b1707226a33aefaf805
SocketDev~socket-patch~H04JFO.dockerbuild
34 KB
sha256:56212407725978b0c4fda09966f3284bb6c72d0992c841f14fb80430ad059d4f
SocketDev~socket-patch~H3D44Y.dockerbuild
17.6 KB
sha256:c03aae47ace37c054c39d94b28431b53bd75acdf3f4650f554b0a605a926b122
SocketDev~socket-patch~I8YIH4.dockerbuild
34.1 KB
sha256:26b71be49e71b262ee84b397c8831c8f256680f67a1bdab128cc57ae1e651f5c
SocketDev~socket-patch~KNKSGA.dockerbuild
21.1 KB
sha256:9483048116eaca5de915c4b8f208774ec7fc23340a65326dadc303f8a34c7959
SocketDev~socket-patch~L0S476.dockerbuild
33.6 KB
sha256:d1c923f207e8243cf8473374c8de70182712a320e5d9e09b6c3270be2e8cf889
SocketDev~socket-patch~LCESSQ.dockerbuild
33.3 KB
sha256:c894c459194290ecb41195ea3d60e7530bc7d7725d90093c1f78741945d40cbf
SocketDev~socket-patch~LLK3SU.dockerbuild
11.4 KB
sha256:d669b3d51ffa06cbb9e4287eba59146facdee8b7d1c798b1ad2f5c5314e56a45
SocketDev~socket-patch~LN15F8.dockerbuild
33.1 KB
sha256:3a26eba9a73f916d2700693e3bc5a168e0fbbd58d338cc2de22d6bf2f2ce16fc
SocketDev~socket-patch~LQWQOO.dockerbuild
33.1 KB
sha256:4720ffa2c5291b5c9b8ba8e611e6acf48fb960420e474ca73370753c3b1208a9
SocketDev~socket-patch~ME261D.dockerbuild
33.6 KB
sha256:f0cd9e76bb21111f91c59eb04fdaf4a940ba254b2f2ba238938ba5b268d6361a
SocketDev~socket-patch~MPDMDR.dockerbuild
34 KB
sha256:17e5e5afd891dc278f7584c179097496ce9590abc844eb9d005ed57213009b06
SocketDev~socket-patch~N3D484.dockerbuild
16.5 KB
sha256:8c7dfcd75112e5329a2b8139a2190f5ac594933a8500521740a1cb66a5feafc1
SocketDev~socket-patch~ODS5BN.dockerbuild
16.8 KB
sha256:2b996c951fabf645895d8a455679c3a8a91b8681aa085c21f1d009f5c7f6d466
SocketDev~socket-patch~QPTUB7.dockerbuild
11.4 KB
sha256:7e023b8d540730076d2e4a16c0aa691852a637d59db06a51648ea30a176e9fe7
SocketDev~socket-patch~RHRVP7.dockerbuild
20.4 KB
sha256:f42fe207fb3b0dd042d7ac71758aac781657828ed16cd7d878d299402ab8f897
SocketDev~socket-patch~RW0ONS.dockerbuild
32.8 KB
sha256:203e8e001376c657b52d7798494479b0487bacedca6670a3805bdbcd53c709a8
SocketDev~socket-patch~S3J27W.dockerbuild
33.6 KB
sha256:a6d32aea5ed9aa2d1815e21731453c9a223afad768c58f0d033ff1347cd27c04
SocketDev~socket-patch~SVHR5R.dockerbuild
24.1 KB
sha256:09369aa8d163876c3e82c747375a445d64eff00eec5e94143488e0686882ec1f
SocketDev~socket-patch~UN0FTE.dockerbuild
20.3 KB
sha256:a065c657964746ac9199066ecbb9e143697b94a1e6d609dde64ecee8b1841b99
SocketDev~socket-patch~VMMD0W.dockerbuild
22.1 KB
sha256:304b1927f20997c1e34181a48d6ac80b0f86d5f89126c06a52edd2e53f9f494d
SocketDev~socket-patch~W1FZMN.dockerbuild
33.9 KB
sha256:0406b12f7cb6918d5d7c04e503a3c6bfbcd755329e08c969d09880774a8cf369
SocketDev~socket-patch~X4G0Q3.dockerbuild
18.7 KB
sha256:11b3292529038d0c97da53e82dc10ee60e5b3eed94851352c2db7e2c9ce16592
SocketDev~socket-patch~YAATN2.dockerbuild
21.4 KB
sha256:cddbfa40c6bfe43fad59b16bb750763434cf7fc87483565390bdc1f67915fa72
coverage-docker-cargo Expired
30.3 KB
sha256:350b2fc762d7f5ce08166681810d1431c7e8455595a3edcf0035e5ca84792403
coverage-docker-composer Expired
30.3 KB
sha256:9e5a0a4c452ab8c734699510f24cbd866dc99f588a931dd212cac837aeb4084d
coverage-docker-deno Expired
30.3 KB
sha256:71305b6d63245d65dce4bf08899fe067623e996a7f224add6054ed4ff984b8bb
coverage-docker-gem Expired
30.3 KB
sha256:2071668a40cd6cf5c83b918f68cba0c2fa454cafec4500edc7943c9f3a2d83ee
coverage-docker-golang Expired
30.3 KB
sha256:5f60adf44d27a2466f19968854d7b1ac7ece798cc150dde53fe752adb43d4418
coverage-docker-maven Expired
30.3 KB
sha256:938b8a0d2a8bf60d20df120a626273b9bb53d6684fe956ac36b4e4d0dac4695a
coverage-docker-npm Expired
30.3 KB
sha256:3b487423217c06609ee4974669a79485088039fef838adad1a07ab33b34cb436
coverage-docker-nuget Expired
30.3 KB
sha256:96ade829de8f3045bd4e8b4d649e93bf0278778fa45d04e2c7a2484d6499315b
coverage-docker-pypi Expired
30.3 KB
sha256:59346ab1d55403c2bfdc6ca1706d443c371f5f518f8d5a33f43f9ea67ecaf00e
coverage-host Expired
91.7 KB
sha256:4980875d2fa4eef68d39bcd52203662431c808b4a41b14493dd752edb17eed90
coverage-lcov Expired
95 KB
sha256:ce8ea4b491a887886c5aa0b4d959bd6bab3f92c5c9f8b035d0c7ed25fae99c6e