Repository navigation
Bump typescript from 5.9.3 to 6.0.3 #3
Triggered via pull request
September 27, 2026 17:52
dependabot[bot]
Status
Failure
Total duration
1m 46s
Artifacts
–
ci.yml
on: pull_request
Typecheck, lint, test & build
1m 42s
Validate docker-compose.yml
6s
Annotations
1 error and 4 warnings
|
Typecheck, lint, test & build
Process completed with exit code 1.
|
|
Typecheck, lint, test & build:
src/lib/api-client.ts#L29
Do not use `window.location.href` to navigate to internal Next.js pages. Use `redirect()` in the render phase, or `useRouter().push()` in Client Components' event handlers instead. See: https://nextjs.org/docs/messages/no-location-assign-relative-destination
|
|
Typecheck, lint, test & build:
src/components/onboarding/pending-invitations.tsx#L29
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
|
|
Typecheck, lint, test & build:
src/components/app/user-menu.tsx#L120
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
|
|
Typecheck, lint, test & build:
src/app/invite/[token]/page.tsx#L94
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
|