Skip to content
Build FreeBSD Container

chore: add appjail director support & regen docs #38

Sign in to view logs

chore: add appjail director support & regen docs

chore: add appjail director support & regen docs #38

Triggered via push March 20, 2026 10:46
@ahzeahze
pushed 7be7361
main
Status Success
Total duration 8m 24s
Artifacts 6

build.yaml

on: push
build  /  detect
7s
build / detect
Matrix: build / build
build  /  test-compose
0s
build / test-compose
build  /  commit-sbom
4s
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. 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 (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 (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
79.7 KB
sha256:f2ac0332494c83cdf4d640eec83a056bd1b4e92015b1796892b53582db4b0306
cit-results-pkg Expired
79.6 KB
sha256:912a340132ac8168937858a50b84249ae1fe1a5c35576951165639dede0f43c1
cit-results-pkg-latest Expired
79.7 KB
sha256:fb1f6b1dfb4648117f6dc48cf73b27205c7c7b0b5aa85d8f58dadb932f0d3fa4
sbom-latest
2.27 KB
sha256:83bfa853622e3d34f1e43d82b5bd4b2da41306989ea54afb614a00e30b926e59
sbom-pkg
2.14 KB
sha256:cf91b3ad05de4d664b2cd8e44fc57046a0d1046bd318bd1b29dc5ef3a6379d99
sbom-pkg-latest
2.18 KB
sha256:7dbfa98fe91ae70e3158badb19a9ef941394d464f99a9c44bf2621d48a371e57