Skip to content

Merge pull request #11404 from neinteractiveliterature/renovate/puma-… #25035

Merge pull request #11404 from neinteractiveliterature/renovate/puma-…

Merge pull request #11404 from neinteractiveliterature/renovate/puma-… #25035

Triggered via push April 30, 2026 17:33
Status Success
Total duration 5m 35s
Artifacts 10

ci.yml

on: push
Test coverage report
16s
Test coverage report
Update release draft
18s
Update release draft
Fit to window
Zoom out
Zoom in

Annotations

13 warnings
The 'as' keyword should match the case of the 'from' keyword: Dockerfile.assets#L3
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Default value for global ARG results in an empty or invalid base image name: Dockerfile.assets#L3
InvalidDefaultArgInFrom: Default value for ARG ${BASEIMAGE} 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/
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#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#L50
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/
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/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L39
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#L62
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#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#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/
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. 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
coverage-main
90.6 KB
sha256:1bea379c4b24e44cc2ed29ef341d5aca9b0e3b19d779beb181ca61c18592aa9f
doc-site
6.1 MB
sha256:8686fdebe04706f13f553f3acc7cda3d0336ddf250add8cc5f85be8bb9fbd3ef
minitest-coverage
50.7 KB
sha256:831637cb4dca0ff1475165081d449f6ed2041fc80cb78e11b8f358f12ff15fa7
minitest-reports
28.2 KB
sha256:171785c97f9268c643d4be1a1b7f88461562a85899f4da02ab9689df551327b2
minitest-system-coverage
31.3 KB
sha256:bbec55b7a9e7d2fe5e2be0651247369b11b2d60159033308b983ba0c86fd1e33
minitest-system-reports
973 Bytes
sha256:d1ea835a35b3ce52c6d5d5e45e8aeed38a3c34b936b70b165eacd788a7b30f18
neinteractiveliterature~intercode~CB2OF6.dockerbuild
44.7 KB
sha256:5f938b4a7984a3cf651afdc2964847552555ebc854f18f464bfc6f62c9682e64
neinteractiveliterature~intercode~S6NL9O.dockerbuild
142 KB
sha256:89c7eff6c819ffd4e6170062e72754de1ccc2d3d47088f5697397083a7ea60fe
vitest-coverage
88 KB
sha256:b0807170ca2319b2e04fc922e28fe33b79f7c9235b152592c8daef5a180b88cf
vitest-reports
547 KB
sha256:7cba23b3dba5daaa1ab13d36a692855ae53815532050caf8bf7db015fc69104f