Skip to content

Update dependency react-router to v7.14.2 #25063

Update dependency react-router to v7.14.2

Update dependency react-router to v7.14.2 #25063

Triggered via pull request April 30, 2026 17:46
Status Failure
Total duration 14m 27s
Artifacts 7

ci.yml

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

Annotations

3 errors and 11 warnings
TypeScript check
Process completed with exit code 2.
TypeScript check: app/javascript/TicketTypeAdmin/loaders.tsx#L68
Argument of type '{ params: { eventId: string | undefined; }; request: Request; context: any; unstable_pattern: string; }' is not assignable to parameter of type 'LoaderFunctionArgs<RouterContextProvider>'.
TypeScript check: app/javascript/TicketTypeAdmin/loaders.tsx#L53
Argument of type '{ params: {}; request: Request; context: any; unstable_pattern: string; }' is not assignable to parameter of type 'LoaderFunctionArgs<RouterContextProvider>'.
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/
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#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/
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/
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#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#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/
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/
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/

Artifacts

Produced during runtime
Name Size Digest
minitest-coverage
50.7 KB
sha256:8763d0ca3c6f6a721255000c2d947bb10bac1673d3b2c331a990519f960a6427
minitest-reports
28.1 KB
sha256:67ace6cd9c1ebc99c7c6a0947e7feae5a4acba62749ca1394dd922de4ae9a202
minitest-system-coverage
31.3 KB
sha256:ac692f0698a43ea384cc74ecb8e3046f606e2845cb108e966b3c1e00556b72b1
minitest-system-reports
974 Bytes
sha256:630a6183bcf94d8f0b639aa91aaa084d6d0179416a1db61baf451724e3903e9f
neinteractiveliterature~intercode~URF130.dockerbuild
136 KB
sha256:07bc91f28e2ca7b284a9e66fc500ae74f9f868c0e058993fcd30dcc6678dcbfa
vitest-coverage
88 KB
sha256:d8dd78d5de21ec712098557294447e46aa426e4d92183e61b39bfa9d5f389875
vitest-reports
546 KB
sha256:831d25d7888dc86b090e959356bf5638b827441436665150d5d387ba9fd8995c