Update dependencies to the latest version #130
imbhargav5
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
Annotations
4 errors and 7 warnings
|
Build with 18.x
Process completed with exit code 1.
|
|
Run all tests (18.x):
src/components/ui/Dialog/Dialog.tsx#L28
'children' is defined but never used
|
|
Run all tests (18.x):
src/components/ui/Sheet/Sheet.tsx#L44
'children' is defined but never used
|
|
Run all tests (18.x)
Process completed with exit code 1.
|
|
Build with 18.x
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Build with 18.x
The following actions uses node12 which is deprecated and will be forced to run on node16: lannonbr/[email protected], actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Run all tests (18.x)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Run all tests (18.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: lannonbr/[email protected], actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Run all tests (18.x):
src/app/MobileNavigation.tsx#L81
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Run all tests (18.x):
src/app/Navbar.tsx#L44
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Run all tests (18.x):
src/app/Navbar.tsx#L61
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|