Skip to content

feat(vex): OpenVEX 0.2.0 attestation generator #216

feat(vex): OpenVEX 0.2.0 attestation generator

feat(vex): OpenVEX 0.2.0 attestation generator #216

Triggered via pull request May 24, 2026 22:01
Status Failure
Total duration 16m 20s
Artifacts 47

ci.yml

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

Annotations

3 errors, 17 warnings, and 1 notice
test (ubuntu-latest)
Process completed with exit code 101.
test (macos-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 (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 (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 (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 (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 (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 (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 (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/
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 (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~1CGJRD.dockerbuild
33.8 KB
sha256:0e3d18bf40147322d47f36ec4d5c56f819d697268dc77e8fea59d74a9cc9aefc
SocketDev~socket-patch~2938EU.dockerbuild
34.2 KB
sha256:8fe11d56142f452b26961f436669c44034b286d6e78b67c1aa5175841e5a8a74
SocketDev~socket-patch~3OEONP.dockerbuild
21.9 KB
sha256:8d4bde71bccab3bb3cec2181c0cf6d6652dad8db9970fddf4e0d1a8ad2002227
SocketDev~socket-patch~6EMHXA.dockerbuild
23.8 KB
sha256:452e7dde8e14d64cc97bf37327b6994fb6ccaa71036863bbd241ff0b48ca7e30
SocketDev~socket-patch~91FW7S.dockerbuild
16.4 KB
sha256:70d4b0b9df918f1c2dd243ee4b170fff062f8e91adf06c726d555566180288da
SocketDev~socket-patch~AH2HX8.dockerbuild
32.5 KB
sha256:fbfca30a1ad73f2bf5f366d19568f96e095fb57b7395b1e7036b953a54074c35
SocketDev~socket-patch~B3C8UX.dockerbuild
33.4 KB
sha256:a27ecdf3d305d90c7bbe3ddc7a43b8656d3c0d9de50de936795aff01c7f36676
SocketDev~socket-patch~B9UD6Q.dockerbuild
33.1 KB
sha256:29d779220400c97bd5c77b384c928174a38bb778f13c9239be261e59c012756d
SocketDev~socket-patch~BW9KHG.dockerbuild
19.8 KB
sha256:4f5f9255eff0fe85235c1425ddc67c7232ea6736b08b5646034bdd882e395960
SocketDev~socket-patch~E1SZY9.dockerbuild
33.5 KB
sha256:e1383883789c06f90f255db201a8c79fa27e435a691ee8b587cc5970cba671a1
SocketDev~socket-patch~G8ZY7M.dockerbuild
33.4 KB
sha256:3cf12ae215f38ad52d7a7f43f23b46c9a696916b5b1862b9fab831e7db1e3666
SocketDev~socket-patch~GX6VA2.dockerbuild
34 KB
sha256:88cec9729cd9d507505507f73be443b4105eafff1c61ef8f9fd65ff99194ba31
SocketDev~socket-patch~H6M1P3.dockerbuild
33.4 KB
sha256:97dc446f1a4931a8a701d6407cb45372ba8f4c74aae87b8ca0a6e4a8b9e5d335
SocketDev~socket-patch~HJ3RQQ.dockerbuild
21.4 KB
sha256:78a1d0306b81f383e8977f5b8a6cc378d57b0f264e3229aa66b3510cc6cdaa0e
SocketDev~socket-patch~HN7M3V.dockerbuild
17.1 KB
sha256:2205f65e28272c964841f9041239152cf528671a3d88b37d0dc23ea50ad2d60e
SocketDev~socket-patch~IMS1KI.dockerbuild
20.4 KB
sha256:a4c71cf7280856aafa997bba65900827bd38db2909d63ceec47f712d48dbcc14
SocketDev~socket-patch~JDGIBM.dockerbuild
19.7 KB
sha256:5c9808415eff9aa8f7b3ca1d1026cb9bc996b35769a4eade8b4d29b3e231cdea
SocketDev~socket-patch~L4C6HQ.dockerbuild
17.7 KB
sha256:4247dfd54b79ccf93dbc649deef647081057a2c942e7578cd801e32cfdc5bd14
SocketDev~socket-patch~LHV3WN.dockerbuild
18.4 KB
sha256:8d2f8a537186ceb212cb82d3d5fec14c082032c61d0af1127a5cb4c325457d30
SocketDev~socket-patch~M9HDFA.dockerbuild
33.5 KB
sha256:f3323c1eadd0dd131fcbebfac61ad133e67a039aa0bb77aeae1e8fd9b5f6a622
SocketDev~socket-patch~N2ONYG.dockerbuild
20.2 KB
sha256:207691f2cab114fd3f48f24cd17072540a7b3deed820dcc73f6baedef6dd624c
SocketDev~socket-patch~N8MZMM.dockerbuild
34 KB
sha256:7897600729eaf392558c6e2d2eb2a79ed27a7b054c97d04e6d9ff3e248218e84
SocketDev~socket-patch~NLT9YZ.dockerbuild
33.6 KB
sha256:2cc5266c1043596cd761d042b07bdd3ed38bf414023cf885c3602c61d6372673
SocketDev~socket-patch~NV6EAX.dockerbuild
23.9 KB
sha256:d51b1cef0a50912a0e5018a1bee4b405025532f840c86a36917a4b73ecd52827
SocketDev~socket-patch~P4883N.dockerbuild
33.8 KB
sha256:8d59ab6fd8296cb2cd655e97f2bd8f432004af50c2ebb6136f66680074ee1b14
SocketDev~socket-patch~PD25OM.dockerbuild
17.1 KB
sha256:300c02cde0bf28d0e56569c75c57ad9d6d9dcac61da4f0aa5003d12eea0430a3
SocketDev~socket-patch~QLN9HA.dockerbuild
20.8 KB
sha256:e21eaa07ed10ee0ba67d6bf8bf2496eadd704dcb03834834fbd91a8b0ef66c8b
SocketDev~socket-patch~QXO9BM.dockerbuild
21.7 KB
sha256:542e97818e40f7b16fed7905103c392371241d0d27efa19432246b0c81a1b3bb
SocketDev~socket-patch~R9WGLY.dockerbuild
33.2 KB
sha256:ad427287d0813389ed357e5442da65a88e9d8fb7e0891f716b1ca014fed9471a
SocketDev~socket-patch~UFF8K6.dockerbuild
10.9 KB
sha256:74623373411f2a9af805bab645908864567a51335c74ec4b704a4b319b38aab0
SocketDev~socket-patch~UH0CZ5.dockerbuild
33.5 KB
sha256:9793d4df8f895e349f8616ab6fe0f7cf56e63e0eac51d29693acd70cec46a823
SocketDev~socket-patch~VDF08C.dockerbuild
33.7 KB
sha256:391e83d6224e9f3c1d9c28d0d534f3478dc20005ebbde9a4e6832f7cf09ff988
SocketDev~socket-patch~WHR96D.dockerbuild
11.1 KB
sha256:6eade5e07572ec9443a8c0d1fb687bafc984882c754649d0899db5cc9bebb87b
SocketDev~socket-patch~WNV8GX.dockerbuild
33.9 KB
sha256:d352a9d7d53e2cbcf3b60a41149c04b6ff7d51384971c0448fef3cbe993c0ec7
SocketDev~socket-patch~X8327I.dockerbuild
33.5 KB
sha256:d1469b638dc96e90f7e638229b44ff54c77d0f79d7338fa062a9384a35ea6160
SocketDev~socket-patch~YWMLIL.dockerbuild
17.9 KB
sha256:6cc0d0baac19e45c19de599882c421e504d4397c8c1ca55b9be0f36ca26557d5
coverage-docker-cargo Expired
30.3 KB
sha256:b1a2e038672fc35017dafa41a613a2449fbfbc4696d774792f641ebadf0b712f
coverage-docker-composer Expired
30.3 KB
sha256:036bf5d67b786c2ca480600694d7eafd8337a61b822999b1b0920c3a5fa2cf44
coverage-docker-deno Expired
30.3 KB
sha256:b0bda40e054a3d53dfbfa82273d32fba2d446b02ff8d6874ba11e0875f1d477f
coverage-docker-gem Expired
30.3 KB
sha256:d866d0ea5efd44abe0c74362a961f7868195722524b973b98c147d8f66208622
coverage-docker-golang Expired
30.3 KB
sha256:fc958a6f0a4ce5fc91c5b6854c1a8b488d10de6373665fc034fd5a607ae2d4b3
coverage-docker-maven Expired
30.3 KB
sha256:c6e2f63b6fe3fce9ba0e54fdc0e4f4d21b8c603458c5b1ac0ff00eb31ed111cf
coverage-docker-npm Expired
30.3 KB
sha256:d0bb0f5e5f456e23c5cc5f855abcbeebf543f01f3a5e8e59bb6df63289fb78b1
coverage-docker-nuget Expired
30.3 KB
sha256:d7b091e00586e46661393431b233efd48cd359ea2fe7d957b8cb0550a7b9c6fe
coverage-docker-pypi Expired
30.3 KB
sha256:9526641f7488ab511a4f557b12125afce5fb5576186e8766a4dd01cb80ddb74e
coverage-host Expired
91.7 KB
sha256:8bc8445f62d2e5b5f0b356dfb683a6369e68378751a4169e56b60e9cc40d8e7f
coverage-lcov Expired
95 KB
sha256:0c1619657ec976c6ab003793df8ecee8a219890d37430f6a3a771b28fc6c0afa