Skip to content

chore: add frozen_string_literal and apt_update to test recipes #161

chore: add frozen_string_literal and apt_update to test recipes

chore: add frozen_string_literal and apt_update to test recipes #161

Triggered via pull request March 19, 2026 11:35
Status Failure
Total duration 35s
Artifacts

ci.yml

on: pull_request
lint-unit  /  ...  /  RSpec ubuntu-latest
27s
lint-unit / runner / RSpec ubuntu-latest
lint-unit  /  ...  /  Cookstyle
28s
lint-unit / runner / Cookstyle
lint-unit  /  ...  /  yamllint
14s
lint-unit / runner / yamllint
lint-unit  /  ...  /  markdownlint
5s
lint-unit / runner / markdownlint
lint-unit  /  ...  /  linkspector
31s
lint-unit / runner / linkspector
lint-unit  /  ...  /  Check Metadata
6s
lint-unit / runner / Check Metadata
Fit to window
Zoom out
Zoom in

Annotations

1 error and 5 warnings
lint-unit / runner / yamllint: ./.rubocop.yml#L3
3:1 [empty-lines] too many blank lines (1 > 0)
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. 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. 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/[email protected], 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/[email protected]. 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/cache@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/