Skip to content

Merge pull request #1034 from KuchiMercy/fe-be-issues #659

Merge pull request #1034 from KuchiMercy/fe-be-issues

Merge pull request #1034 from KuchiMercy/fe-be-issues #659

Triggered via push June 28, 2026 16:05
Status Success
Total duration 1m 3s
Artifacts

CI.yaml

on: push
Format Check
11s
Format Check
Clippy Lint
21s
Clippy Lint
Test Suite
27s
Test Suite
Build Check
10s
Build Check
Build WASM
14s
Build WASM
Backend (NestJS)
49s
Backend (NestJS)
Frontend (Next.js)
1m 0s
Frontend (Next.js)
Fit to window
Zoom out
Zoom in

Annotations

17 warnings
Build Check
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Format Check
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build WASM
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Clippy Lint
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test Suite
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Backend (NestJS)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Frontend (Next.js)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Frontend (Next.js): frontend/hooks/useWebSocket.ts#L171
React Hook useCallback has a missing dependency: 'setNotifications'. Either include it or remove the dependency array
Frontend (Next.js): frontend/hooks/useWebSocket.ts#L166
React Hook useCallback has a missing dependency: 'setNotifications'. Either include it or remove the dependency array
Frontend (Next.js): frontend/hooks/useWebSocket.ts#L159
React Hook useCallback has a missing dependency: 'setNotifications'. Either include it or remove the dependency array
Frontend (Next.js): frontend/hooks/useWebSocket.ts#L85
React Hook useCallback has an unnecessary dependency: 'options.userId'. Either exclude it or remove the dependency array
Frontend (Next.js): frontend/components/ui/command-palette.tsx#L92
The 'results' array makes the dependencies of useCallback Hook (at line 125) change on every render. To fix this, wrap the initialization of 'results' in its own useMemo() Hook
Frontend (Next.js): frontend/app/(dashboard)/print-labels/page.tsx#L55
Expected an assignment or function call and instead saw an expression
Frontend (Next.js): frontend/app/(dashboard)/developer/page.tsx#L54
Expected an assignment or function call and instead saw an expression
Frontend (Next.js): frontend/app/(dashboard)/contracts/page.tsx#L40
The 'contracts' logical expression could make the dependencies of useMemo Hook (at line 55) change on every render. To fix this, wrap the initialization of 'contracts' in its own useMemo() Hook
Frontend (Next.js): frontend/app/(dashboard)/assets/[id]/page.tsx#L928
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
Frontend (Next.js): frontend/app/(dashboard)/assets-bulk/page.tsx#L61
Expected an assignment or function call and instead saw an expression