Skip to content

feat(opsce): integrate Stellar SDK for asset tokenization and impleme… #535

feat(opsce): integrate Stellar SDK for asset tokenization and impleme…

feat(opsce): integrate Stellar SDK for asset tokenization and impleme… #535

Triggered via pull request June 1, 2026 10:36
Status Failure
Total duration 1m 2s
Artifacts

CI.yaml

on: pull_request
Format Check
15s
Format Check
Clippy Lint
59s
Clippy Lint
Test Suite
20s
Test Suite
Build Check
20s
Build Check
Build WASM
23s
Build WASM
Backend (NestJS)
27s
Backend (NestJS)
Frontend (Next.js)
41s
Frontend (Next.js)
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 13 warnings
Format Check
Process completed with exit code 1.
Build Check
Process completed with exit code 101.
Test Suite
Process completed with exit code 101.
Backend (NestJS): backend/src/opsce/users/guards/jwt-auth.guard.ts#L12
'info' is defined but never used
Backend (NestJS): backend/src/opsce/stellar/stellar.service.ts#L298
'args' is defined but never used
Backend (NestJS): backend/src/opsce/stellar/stellar.service.ts#L297
'functionName' is defined but never used
Backend (NestJS): backend/src/opsce/stellar/stellar.service.ts#L86
'minVotingThreshold' is assigned a value but never used
Backend (NestJS): backend/src/opsce/stellar/stellar.service.ts#L85
'decimals' is assigned a value but never used
Backend (NestJS): backend/src/opsce/stellar/stellar.service.ts#L83
'assetIdNum' is assigned a value but never used
Backend (NestJS): backend/src/opsce/stellar/stellar.service.ts#L69
'metadata' is defined but never used
Backend (NestJS): backend/src/opsce/stellar/stellar.service.ts#L68
'pricePerShare' is defined but never used
Backend (NestJS): backend/src/opsce/stellar/stellar.service.ts#L3
'StrKey' is defined but never used
Backend (NestJS): backend/src/opsce/assets/entities/asset.entity.ts#L9
'OneToMany' is defined but never used
Frontend (Next.js)
Process completed with exit code 1.
Clippy Lint
Process completed with exit code 101.
Format Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test Suite
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build WASM
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Backend (NestJS)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. 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 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Frontend (Next.js): frontend/opsce/features/assets/AssetQRCode.tsx#L141
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/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
Clippy Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/