Skip to content

Update dependency rubocop-rspec to v3.9.0 #23876

Update dependency rubocop-rspec to v3.9.0

Update dependency rubocop-rspec to v3.9.0 #23876

Triggered via pull request April 24, 2026 22:17
Status Success
Total duration 27m 22s
Artifacts 7

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
Build containers
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-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/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L55
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L6
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Dockerfile#L96
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L60
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Default value for global ARG results in an empty or invalid base image name: Dockerfile#L50
InvalidDefaultArgInFrom: Default value for ARG ruby:${RUBY_VERSION}-slim results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
Default value for global ARG results in an empty or invalid base image name: Dockerfile#L47
InvalidDefaultArgInFrom: Default value for ARG ruby:${RUBY_VERSION}-slim results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L50
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L38
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AWS_ACCESS_KEY_ID") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Default value for global ARG results in an empty or invalid base image name: Dockerfile#L6
InvalidDefaultArgInFrom: Default value for ARG ruby:${RUBY_VERSION}-slim results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L47
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Test coverage report
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: clearlyip/code-coverage-report-action@v6, marocchino/sticky-pull-request-comment@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/

Artifacts

Produced during runtime
Name Size Digest
minitest-coverage
50.7 KB
sha256:3979213bf06ecbb2665178ad1c8bec4ad221c0f49b0ac377e8370533027f9b17
minitest-reports
28.3 KB
sha256:bbfb9f3544be23887ddb7e28edeab8026d6007023e7e92082c9c465d2c7b102b
minitest-system-coverage
31.3 KB
sha256:1ed3807d064755fbb6ab4dfcaac033586aae9d52039f57687854667f7edfef90
minitest-system-reports
971 Bytes
sha256:4eed623c53a9470238b5c707dba3bef366922c6d3d6697e1004190517f8a33eb
neinteractiveliterature~intercode~TWMNEY.dockerbuild
134 KB
sha256:5e6b54c23b46ff49d043bae465efaa452abc23b68061d860fafaa0575e8a7133
vitest-coverage
88 KB
sha256:e46043e062745dfa7d1de68a8d8ca1db1555f4b4279cf4e618213eef3d5d7fb4
vitest-reports
549 KB
sha256:28c6fcb16474028ae7258de278b8cbcd517177723208a30ffa620bfb6b3f4050