Skip to content
Build FreeBSD Container

Add appjail: and rebuild docs #36

Sign in to view logs

Add appjail: and rebuild docs

Add appjail: and rebuild docs #36

Triggered via push March 17, 2026 15:15
@ahzeahze
pushed 24b4fa4
main
Status Success
Total duration 15m 9s
Artifacts 6

build.yaml

on: push
build  /  detect
7s
build / detect
Matrix: build / build
build  /  test-compose
0s
build / test-compose
build  /  commit-sbom
7s
build / commit-sbom
build  /  create-manifests
build / create-manifests
build  /  notify-status
8s
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 (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-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 / 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:0d12d013d829187e24848cccf0323480ff58aa9efe73d08bd9b5c6c45606f4b1
cit-results-pkg Expired
79.6 KB
sha256:d7344366bddf5802dd5f4c364572bdb7f68808b5f1b1d97f40d5f44c272b9c7c
cit-results-pkg-latest Expired
79.7 KB
sha256:945c1edd94d9969f4329e952b0827ffb9cb044254a935bbd24350de3f6f93a08
sbom-latest
2.28 KB
sha256:fb446439be17f03bb731da9a611c040ae47722f353932d21641f46920dc35e05
sbom-pkg
2.17 KB
sha256:1197391414c81b2bee0644048a875b6833b1b5d751437e355a035bfec63a39b4
sbom-pkg-latest
2.16 KB
sha256:91ae93f756a60557bf5f7fad25b4ec11e86ead88d126c3cd2c94d6b609be1553