Skip to content

fix: add require 'ostruct' for Ruby 3.2+ compatibility (#296) #259

fix: add require 'ostruct' for Ruby 3.2+ compatibility (#296)

fix: add require 'ostruct' for Ruby 3.2+ compatibility (#296) #259

Triggered via push March 16, 2026 10:33
Status Failure
Total duration 6h 5m 54s
Artifacts

ci.yml

on: push
lint-unit  /  ...  /  RSpec ubuntu-latest
26s
lint-unit / runner / RSpec ubuntu-latest
lint-unit  /  ...  /  Cookstyle
30s
lint-unit / runner / Cookstyle
lint-unit  /  ...  /  yamllint
9s
lint-unit / runner / yamllint
lint-unit  /  ...  /  markdownlint
6s
lint-unit / runner / markdownlint
lint-unit  /  ...  /  linkspector
45s
lint-unit / runner / linkspector
lint-unit  /  ...  /  Check Metadata
0s
lint-unit / runner / Check Metadata
Fit to window
Zoom out
Zoom in

Annotations

13 errors and 16 warnings
integration (ubuntu-1804, default)
The process '/usr/bin/kitchen' failed with exit code 1
integration (centos-7, default)
The process '/usr/bin/kitchen' failed with exit code 1
integration (centos-stream-8, default)
The process '/usr/bin/kitchen' failed with exit code 1
integration (debian-11, default)
The process '/usr/bin/kitchen' failed with exit code 1
integration (debian-10, default)
The process '/usr/bin/kitchen' failed with exit code 1
integration-macos (macos-latest, default)
The process '/usr/local/bin/kitchen' failed with exit code 20
integration (almalinux-8, default)
The process '/usr/bin/kitchen' failed with exit code 20
integration (amazonlinux-2, default)
The process '/usr/bin/kitchen' failed with exit code 20
integration (ubuntu-2004, default)
The process '/usr/bin/kitchen' failed with exit code 20
integration (rockylinux-8, default)
The process '/usr/bin/kitchen' failed with exit code 20
integration (fedora-latest, default)
The process '/usr/bin/kitchen' failed with exit code 20
integration (opensuse-leap-15, default)
The process '/usr/bin/kitchen' failed with exit code 20
integration-windows (windows-latest, windows)
The job has exceeded the maximum execution time of 6h0m0s
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. 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 ubuntu-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. 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. 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/setup-node@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/
integration (ubuntu-1804, default)
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, actionshub/test-kitchen@3.0.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/
integration (centos-7, default)
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, actionshub/test-kitchen@3.0.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/
integration (centos-stream-8, default)
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, actionshub/test-kitchen@3.0.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/
integration (debian-11, default)
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, actionshub/test-kitchen@3.0.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/
integration (debian-10, default)
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, actionshub/test-kitchen@3.0.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/
integration-macos (macos-latest, default)
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, actionshub/test-kitchen@3.0.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/
integration (almalinux-8, default)
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, actionshub/test-kitchen@3.0.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/
integration (amazonlinux-2, default)
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, actionshub/test-kitchen@3.0.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/
integration (ubuntu-2004, default)
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, actionshub/test-kitchen@3.0.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/
integration (rockylinux-8, default)
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, actionshub/test-kitchen@3.0.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/
integration (fedora-latest, default)
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, actionshub/test-kitchen@3.0.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/
integration (opensuse-leap-15, default)
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, actionshub/test-kitchen@3.0.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/