feat: build tokenization, governance, and dividends UI components #770
devbackend513-uxCI.yaml
on: pull_request
Format Check
17s
Clippy Lint
29s
Test Suite
40s
Build Check
26s
Build WASM
25s
WASM Size Delta
21s
Backend (NestJS)
29s
Frontend (Next.js)
51s
Annotations
2 errors and 15 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/
|
|
WASM Size Delta
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/
|
|
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/
|
|
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/
|
|
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:182ac40654111a378b83a9b7c45d5f754fa73f7e8e70c4b0d3aced795869df2f
|
|