Skip to content

Build FreeBSD Container #35

Build FreeBSD Container

Build FreeBSD Container #35

Manually triggered March 26, 2026 16:31
Status Success
Total duration 11m 34s
Artifacts 6

build.yaml

on: workflow_dispatch
Matrix: build / build
build  /  test-compose
build / test-compose
build  /  commit-sbom
6s
build / commit-sbom
build  /  create-manifests
0s
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 (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 / 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 (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. 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
413 Bytes
sha256:9420325a0a9cb0510664adbe91e3eee2ed51a0758051454f27a45b809b8c3a07
cit-results-pkg Expired
404 Bytes
sha256:8753c7ab1e3231500e41f9ded2e2b451ccf0c8377170774c888b6f777cdf66bc
cit-results-pkg-latest Expired
423 Bytes
sha256:44151ef9d084523f3486eca5561090b112ccd5585edadc7ef3bf7b5186b3ff42
sbom-latest
4.46 KB
sha256:e603e7fa6a2e3dd7d39d5c532fd03138fb7228b0fb79493f40d2f00c40de43bb
sbom-pkg
4.44 KB
sha256:bf323dd5610dc10c3e86bd5cce1ce664bf55f4254aa45b4b8d5768f43e43deb0
sbom-pkg-latest
4.42 KB
sha256:67bdd476c8f05c5339f64c1f6b7696299dbf8c4abeeb9dbb0ca48be526a80d62