feat!: migrate djbdns to service resources #167
damacusci.yml
on: pull_request
lint-unit
/
...
/
RSpec ubuntu-latest
30s
lint-unit
/
...
/
Cookstyle
10s
lint-unit
/
...
/
yamllint
9s
lint-unit
/
...
/
markdownlint
5s
lint-unit
/
...
/
linkspector
37s
lint-unit
/
...
/
actionlint
12s
lint-unit
/
...
/
Check Metadata
8s
Matrix: integration
Annotations
28 errors and 26 warnings
|
integration (opensuse-leap-16.0, tinydns)
Process completed with exit code 1.
|
|
integration (opensuse-leap-16.0, tinydns)
The process '/usr/bin/kitchen' failed with exit code 1
|
|
integration (fedora-42, source)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (opensuse-leap-16.0, source)
Process completed with exit code 1.
|
|
integration (opensuse-leap-16.0, source)
The process '/usr/bin/kitchen' failed with exit code 1
|
|
integration (debian-13, tinydns)
Process completed with exit code 1.
|
|
integration (debian-13, tinydns)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (debian-13, source)
Process completed with exit code 1.
|
|
integration (debian-13, source)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (ubuntu-2204, source)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (debian-12, source)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (ubuntu-2404, tinydns)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (debian-12, tinydns)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (ubuntu-2204, tinydns)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (almalinux-9, source)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (fedora-42, tinydns)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (ubuntu-2404, source)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (centos-stream-9, source)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (rockylinux-10, source)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (almalinux-9, tinydns)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (centos-stream-10, tinydns)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (amazonlinux-2023, tinydns)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (amazonlinux-2023, source)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (oraclelinux-9, source)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (oraclelinux-9, tinydns)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (centos-stream-9, tinydns)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (centos-stream-10, source)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
integration (rockylinux-10, tinydns)
The process '/usr/bin/kitchen' failed with exit code 20
|
|
lint-unit / runner / RSpec ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SonicGarden/rspec-report-action@v6. 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/
|
|
lint-unit / runner / linkspector
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. 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/
|
|
integration (opensuse-leap-16.0, tinydns)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (fedora-42, source)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (opensuse-leap-16.0, source)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (debian-13, tinydns)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (debian-13, source)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (ubuntu-2204, source)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (debian-12, source)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (ubuntu-2404, tinydns)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (debian-12, tinydns)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (ubuntu-2204, tinydns)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (almalinux-9, source)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (fedora-42, tinydns)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (ubuntu-2404, source)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (centos-stream-9, source)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (rockylinux-10, source)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (almalinux-9, tinydns)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (centos-stream-10, tinydns)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (amazonlinux-2023, tinydns)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (amazonlinux-2023, source)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (oraclelinux-9, source)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (oraclelinux-9, tinydns)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (centos-stream-9, tinydns)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (centos-stream-10, source)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|
|
integration (rockylinux-10, tinydns)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@3.0.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/
|