Skip to content

Merge pull request #11418 from neinteractiveliterature/renovate/strip… #25263

Merge pull request #11418 from neinteractiveliterature/renovate/strip…

Merge pull request #11418 from neinteractiveliterature/renovate/strip… #25263

Triggered via push May 7, 2026 19:16
Status Cancelled
Total duration 4m 42s
Artifacts 9

ci.yml

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

Annotations

3 errors and 11 warnings
Build containers
Canceling since a higher priority waiting request for Continuous integration-refs/heads/main exists
Build containers
The operation was canceled.
Continuous integration
Canceling since a higher priority waiting request for Continuous integration-refs/heads/main exists
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/
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#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/
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/
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/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L37
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/
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/
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/
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/
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#L50
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Artifacts

Produced during runtime
Name Size Digest
coverage-main
90.6 KB
sha256:dde2812d5b5db696900c9ab2905e378f69433881cf7dc6e86e3fdc6d984345ab
doc-site
6.14 MB
sha256:2f22ee8c86bae63adee4eabaa8ad2d2244495e07743a6af8db3803bbdf8f23e3
minitest-coverage
50.7 KB
sha256:446b7943b9fbdd35851622aa21abfba6bb4a0f221094b5e2aa91c2a160394f59
minitest-reports
28.3 KB
sha256:ccb644362b8596d1716f07eabd470156686bbd34b773f875205aca202913a401
minitest-system-coverage
31.3 KB
sha256:2f44d524262991b7f0cd373e6003e8b2e7d5a95c8437c43a68047e69a72e155e
minitest-system-reports
974 Bytes
sha256:d8516f60556da6b84f7336d32f7fb32ef4fc7df68261100d20b4367c6917eb27
neinteractiveliterature~intercode~YGJXSG.dockerbuild
141 KB
sha256:ae550ed9d7c57b19cd4436e1c21228699a951c3285a8e33f14a272e72b086bfc
vitest-coverage
88.1 KB
sha256:dffd561ff31a6ac6b40c4cba7203b7af94172a4d98c4c41ac2be18187559b1ee
vitest-reports
545 KB
sha256:95d8ce77dd961323f59c06cbb3a141943aecb46c29526d6697e95c68d7720efd