Skip to content

Sync with latest changes in dbuild #33

Sync with latest changes in dbuild

Sync with latest changes in dbuild #33

Triggered via pull request March 17, 2026 01:36
Status Success
Total duration 5m 2s
Artifacts 2

build.yaml

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

Annotations

2 errors and 3 warnings
build / build (pkg, Containerfile.pkg, amd64, latest, false, app, rsync)
Process completed with exit code 3.
build / build (pkg-latest, Containerfile.pkg, amd64, 15-latest, false, app, rsync)
Process completed with exit code 3.
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, 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-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/

Artifacts

Produced during runtime
Name Size Digest
cit-results-pkg Expired
407 Bytes
sha256:f2cf51be937b4bba13cdaf3932978cc4cb61ef1a4adde16c2d82aa8c3cb94eb2
cit-results-pkg-latest Expired
425 Bytes
sha256:e56c19469bf72f4e99e1f455d8aa36cd8a2e6b8cff0514f465591362829e3a5a