Update dependency minitest-focus to v1.4.1 #23891
renovate[bot]ci.yml
on: pull_request
TypeScript check
55s
Build containers
3m 44s
Build doc site
3m 17s
Test coverage report
20s
Update release draft
0s
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#L50
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/
|
|
Legacy key/value format with whitespace separator should not be used:
Dockerfile#L38
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/
|
|
Legacy key/value format with whitespace separator should not be used:
Dockerfile#L36
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/
|
|
Legacy key/value format with whitespace separator should not be used:
Dockerfile#L61
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/
|
|
Sensitive data should not be used in the ARG or ENV commands:
Dockerfile#L39
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AWS_SECRET_ACCESS_KEY")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
|
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:2bdc29914bf771b1d4ec09cc4b96d237c98414768dd038481dc8a11e1b42d7d2
|
|
|
minitest-reports
|
28.2 KB |
sha256:620696565a2314b4593abf2a5662344c7764c209d66903b717a63f5e89589a47
|
|
|
minitest-system-coverage
|
31.3 KB |
sha256:d0c2d631ca759da43868ae5722f201d1b8edb32820d41a02265867ed5e9632ca
|
|
|
minitest-system-reports
|
973 Bytes |
sha256:504dd204bb0fca9941d7504198af2e95e3cdbdfbd52eb827f5699380a1330ba7
|
|
|
neinteractiveliterature~intercode~9W0T1E.dockerbuild
|
133 KB |
sha256:05612ea59fd583b303cd82050ee3e5454fdd8844ac297b839fbd8a1572f77e0b
|
|
|
vitest-coverage
|
87.9 KB |
sha256:34011cb77684a1577aa76c8d662a76a9a3ac8121a57f1b7901fc14abd5819e54
|
|
|
vitest-reports
|
548 KB |
sha256:3a3a43774726ae24bed31207b4d1d6948d24832c9b2ec2618dd64662095e2877
|
|