Skip to content
Build FreeBSD Container

Build FreeBSD Container #37

Sign in to view logs

Build FreeBSD Container

Build FreeBSD Container #37

Manually triggered March 19, 2026 08:30
@ahzeahze
⁠ 8ccba61
main
Status Success
Total duration 7m 55s
Artifacts 6

build.yaml

on: workflow_dispatch
build  /  detect
7s
build / detect
Matrix: build / build
build  /  test-compose
0s
build / test-compose
build  /  commit-sbom
6s
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. 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. 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. 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. 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. 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 Expired
414 Bytes
sha256:c78db5f4d64a55e30ceca15fadae943c2d42a771bf24bf7f8564a8f49d0c2ef2
cit-results-pkg Expired
408 Bytes
sha256:8bb4c417b046acbad3dbe965494b54c9388d03b68b479cd205571696052cad14
cit-results-pkg-latest Expired
426 Bytes
sha256:a22d91ef2c34157582b39e408029deda9538591117cc4d8c3c6c8dc996307895
sbom-latest
3.37 KB
sha256:ca792dd92780821f4464065b53fba6773baba264f3fd6c7774995ec913ceb7ef
sbom-pkg
3.33 KB
sha256:ec08f2a1c3f1f5554f84c277b70d373b432535046ec41e09437020c5f1aff5a0
sbom-pkg-latest
3.4 KB
sha256:83999024bfc822f529b1d81ed4a706ad3d69fc99d1f3517bacd9a7e6bf300004