Skip to content

CI

CI #11405

Triggered via schedule March 16, 2026 06:37
Status Success
Total duration 2h 29m 7s
Artifacts 14

ci.yaml

on: schedule
define-scanner-job-matrix
4s
define-scanner-job-matrix
pre-build-updater
3m 41s
pre-build-updater
Matrix: pre-build-scanner
generate-genesis-dump
22m 48s
generate-genesis-dump
Matrix: generate-scanner-bundle
generate-db-dump
1h 43m
generate-db-dump
build-and-push-vulnerabilities-image
5m 41s
build-and-push-vulnerabilities-image
generate-scanner-db-bundle
2m 15s
generate-scanner-db-bundle
upload-db-dump
1m 44s
upload-db-dump
upload-dumps-for-downstream
1m 56s
upload-dumps-for-downstream
upload-dumps-for-embedding
1m 43s
upload-dumps-for-embedding
Matrix: build-images
push-manifests
8m 6s
push-manifests
send-notification
0s
send-notification
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
diff-dumps
No files were found with the provided path: /tmp/diff-dumps-inspect. No artifacts will be uploaded.
build-and-push-vulnerabilities-image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-qemu-action@v3. 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/
build-images (linux, amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-qemu-action@v3. 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/
build-images (linux, ppc64le)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-qemu-action@v3. 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/
build-images (linux, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-qemu-action@v3. 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/
build-images (linux, s390x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-qemu-action@v3. 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
db-dump
501 MB
sha256:6ae1fe9863fdb41d90b78bec93f61cbc87274e7c9c0db65fd8bf3d551d8b1a3b
genesis-dump
259 MB
sha256:10d613ec048de9c4cdf61c236a54dec7db1cbf6316436bd364eac9dbe2216961
offline-dump
712 MB
sha256:f713be0252dc2b277059af49695a82ab07c6ca600aae3ee1900c6b466f8d5739
scanner-build-linux-amd64
43.2 MB
sha256:438c7d0838c71db4469846b52ad1434990761686107197ccbc7676c7c56eaee9
scanner-build-linux-arm64
39.9 MB
sha256:d81edfdeb324cda35109f00c40a3cc8fe0118eece0d5cb49fb138128e89a4b6d
scanner-build-linux-ppc64le
39.9 MB
sha256:cb1019a7a4435c4075e6905b14083de762bd9e145f92203a2e4d5720367fe7e1
scanner-build-linux-s390x
43 MB
sha256:da90224ee34edf884c99a2bd81405e0c35805668c91125db91540763fa93b34c
scanner-bundle-linux-amd64
92.3 MB
sha256:386af0730a42accea8a5ecbf4b0747ac885086e9db58e9bceafb9dc23761a0b1
scanner-bundle-linux-arm64
89 MB
sha256:0a717120c52a20e01cbd192fa24bc9305c594c21f0f7d1ea04004316c8f1d7f6
scanner-bundle-linux-ppc64le
89 MB
sha256:b23fdb1c38e58ab772df5c2aed0f4eb402f8aba3e8cfc6ba8f5425d3d72c6673
scanner-bundle-linux-s390x
92.1 MB
sha256:19b0e9a1e8cffc5dc7425cdf5f19a57786074cf19022b9601b20784e7dc60fb9
scanner-db-bundle
501 MB
sha256:747168035e133c6ffa7d93dc5182f46f8962f4ab0259e191b9590f2002e05819
updater-build
41.7 MB
sha256:ed9c29aa358f68f68a156bc858c983f70edaa8c2c3fd49717417fcf9d34c7200
vuln-dump
45.8 MB
sha256:10e8ae8ed7ce40c731aa37a2b977e05c67e8ae37d46ec8694afcd7faad208923