Skip to content

feat: add feat: enhance dispute resolution UI with detailed view, evi… #38

feat: add feat: enhance dispute resolution UI with detailed view, evi…

feat: add feat: enhance dispute resolution UI with detailed view, evi… #38

Re-run triggered April 26, 2026 08:31
Status Failure
Total duration 28s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
build
Process completed with exit code 1.
build: components/dashboard/dispute-form.tsx#L393
`'` can be escaped with `'`, `‘`, `'`, `’`
build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. 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/
build: components/dashboard/dispute-form.tsx#L445
img elements must have an alt prop, either with meaningful text, or an empty string for decorative images
build: components/dashboard/dispute-form.tsx#L445
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
build: components/dashboard/dispute-details-dialog.tsx#L52
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element