Skip to content

Merge pull request #1249 from KuchiMercy/main #747

Merge pull request #1249 from KuchiMercy/main

Merge pull request #1249 from KuchiMercy/main #747

Triggered via push July 29, 2026 15:15
Status Failure
Total duration 5m 16s
Artifacts 1

CI.yaml

on: push
Format Check
15s
Format Check
Clippy Lint
1m 26s
Clippy Lint
Test Suite
1m 25s
Test Suite
Build Check
32s
Build Check
Build WASM
29s
Build WASM
WASM Size Delta
WASM Size Delta
Backend (NestJS)
47s
Backend (NestJS)
Frontend (Next.js)
5m 8s
Frontend (Next.js)
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 14 warnings
Backend (NestJS)
Process completed with exit code 1.
Frontend (Next.js)
Process completed with exit code 1.
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, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
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/
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/
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/
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/
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/components/ui/avatar.tsx#L6
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/[id]/page.tsx#L507
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

Artifacts

Produced during runtime
Name Size Digest
contract-wasm Expired
88.6 KB
sha256:2ae08ea6dceafdb129bac1a2911abf613adc52553725988f81f839b3325b12f4