Skip to content

chore: bump typescript from 5.9.3 to 6.0.3 #321

chore: bump typescript from 5.9.3 to 6.0.3

chore: bump typescript from 5.9.3 to 6.0.3 #321

Triggered via push July 2, 2026 18:48
Status Success
Total duration 28s
Artifacts

test-format.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Linting: src/app/setup/setup-card.tsx#L59
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
Linting: src/app/setup/page.tsx#L33
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
Linting: src/app/login/login-card.tsx#L34
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
Linting: src/app/(app)/about/page.tsx#L45
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
Linting: src/app/(app)/about/page.tsx#L40
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
Linting: src/app/(app)/about/page.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
Linting: src/app/(app)/about/page.tsx#L18
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