Skip to content

docs: add screenshots & regenerate README #40

docs: add screenshots & regenerate README

docs: add screenshots & regenerate README #40

Triggered via push March 28, 2026 16:22
Status Success
Total duration 21m 14s
Artifacts 6

build.yaml

on: push
Matrix: build / build
build  /  test-compose
0s
build / test-compose
build  /  commit-sbom
4s
build / commit-sbom
build  /  create-manifests
build / create-manifests
build  /  notify-status
3s
build / notify-status
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
build / detect
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 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/
build / build (pkg, Containerfile.pkg, amd64, false, app, rsync)
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/upload-artifact@v4, vmactions/freebsd-vm@v1.4.0. 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/
build / build (latest, Containerfile, amd64, false, app, rsync)
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/upload-artifact@v4, vmactions/freebsd-vm@v1.4.0. 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/
build / build (pkg-latest, Containerfile.pkg, amd64, 15-latest, false, app, rsync)
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/upload-artifact@v4, vmactions/freebsd-vm@v1.4.0. 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/
build / commit-sbom
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/download-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/

Artifacts

Produced during runtime
Name Size Digest
cit-results-latest
85.6 KB
sha256:bb1dce384e5bc7e5fa776b7f87df50256c3d71ce34fe52d3f88979cf22e026e6
cit-results-pkg
85.5 KB
sha256:b85e442e76a34cb1fd325a6da6f6d76e4d105fb9862bbfa4b549f5de4baac53c
cit-results-pkg-latest
85.6 KB
sha256:84c0b03014a1c6b9a73f8b684507bc4597b5b1943ff067b1555357a067216fd3
sbom-latest
2.54 KB
sha256:322c74d247cbe906fdb4fdfa62e9974b285b2c1181943eb22083bdee57786dc2
sbom-pkg
2.1 KB
sha256:4d20243fc6009fba8366d9a53f1219991da154795be612161cd08c47c49273b1
sbom-pkg-latest
2.26 KB
sha256:ec4ef7dacc05f56bf65324d5ab19250724cc2378c539ab4e7154e252ab6c4baa