Skip to content

feat!: migrate to custom resources #242

feat!: migrate to custom resources

feat!: migrate to custom resources #242

Triggered via pull request April 20, 2026 16:25
Status Failure
Total duration 7m 54s
Artifacts

ci.yml

on: pull_request
lint-unit  /  ...  /  RSpec windows-latest
3m 58s
lint-unit / runner / RSpec windows-latest
lint-unit  /  ...  /  Cookstyle
26s
lint-unit / runner / Cookstyle
lint-unit  /  ...  /  yamllint
12s
lint-unit / runner / yamllint
lint-unit  /  ...  /  markdownlint
6s
lint-unit / runner / markdownlint
lint-unit  /  ...  /  linkspector
42s
lint-unit / runner / linkspector
lint-unit  /  ...  /  Check Metadata
7s
lint-unit / runner / Check Metadata
Fit to window
Zoom out
Zoom in

Annotations

1 error and 6 warnings
integration-windows (windows-2019, default)
The process 'C:\cinc-project\cinc-workstation\bin\kitchen.bat' failed with exit code 20
lint-unit / runner / Check Metadata
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: damacus/check-chef-metadata-action@v2. 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 / markdownlint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: DavidAnson/markdownlint-cli2-action@v20. 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 / Cookstyle
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/chef-install@3.0.1. 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/
lint-unit / runner / RSpec windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/chef-install@3.0.1, 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/
integration-windows (windows-2019, default)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actionshub/test-kitchen@main. 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/