feat(marketplace): GitHub Repo Marketplace - Bounty #857 #960
zhaog100ci.yml
on: pull_request
Backend Lint (Ruff)
6s
Backend Tests (pytest)
6s
Contracts Check (Anchor)
13m 57s
Rust Lint (Clippy)
14s
Frontend Setup Check
3s
Frontend Lint (ESLint)
12s
Frontend Type Check (tsc)
16s
Frontend Tests (Vitest)
17s
Frontend Build (Next.js)
21s
CI Status Summary
2s
Annotations
27 errors and 9 warnings
|
Backend Lint (Ruff)
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/solfoundry/solfoundry/backend'. No such file or directory
|
|
Backend Tests (pytest)
No file in /home/runner/work/solfoundry/solfoundry matched to [backend/requirements.txt or **/pyproject.toml], make sure you have checked out the target repository
|
|
Rust Lint (Clippy)
Process completed with exit code 1.
|
|
Rust Lint (Clippy)
Process completed with exit code 101.
|
|
Frontend Type Check (tsc)
Cannot find module '../../lib/animations' or its corresponding type declarations.
|
|
Frontend Type Check (tsc)
Cannot find module '../../lib/animations' or its corresponding type declarations.
|
|
Frontend Type Check (tsc)
Cannot find module '../../lib/utils' or its corresponding type declarations.
|
|
Frontend Type Check (tsc)
Cannot find module '../../lib/animations' or its corresponding type declarations.
|
|
Frontend Type Check (tsc)
Cannot find module '../../lib/animations' or its corresponding type declarations.
|
|
Frontend Tests (Vitest)
Process completed with exit code 1.
|
|
Frontend Type Check (tsc)
Cannot find module '../../lib/animations' or its corresponding type declarations.
|
|
Frontend Type Check (tsc)
Cannot find module '../../lib/utils' or its corresponding type declarations.
|
|
Frontend Type Check (tsc)
Cannot find module '../../lib/animations' or its corresponding type declarations.
|
|
Frontend Type Check (tsc)
Cannot find module '../../lib/utils' or its corresponding type declarations.
|
|
Frontend Type Check (tsc)
Cannot find module '../../lib/animations' or its corresponding type declarations.
|
|
Frontend Build (Next.js)
Cannot find module '../../lib/animations' or its corresponding type declarations.
|
|
Frontend Build (Next.js)
Cannot find module '../../lib/animations' or its corresponding type declarations.
|
|
Frontend Build (Next.js)
Cannot find module '../../lib/utils' or its corresponding type declarations.
|
|
Frontend Build (Next.js)
Cannot find module '../../lib/animations' or its corresponding type declarations.
|
|
Frontend Build (Next.js)
Cannot find module '../../lib/animations' or its corresponding type declarations.
|
|
Frontend Build (Next.js)
Cannot find module '../../lib/animations' or its corresponding type declarations.
|
|
Frontend Build (Next.js)
Cannot find module '../../lib/utils' or its corresponding type declarations.
|
|
Frontend Build (Next.js)
Cannot find module '../../lib/animations' or its corresponding type declarations.
|
|
Frontend Build (Next.js)
Cannot find module '../../lib/utils' or its corresponding type declarations.
|
|
Frontend Build (Next.js)
Cannot find module '../../lib/animations' or its corresponding type declarations.
|
|
Contracts Check (Anchor)
Process completed with exit code 1.
|
|
CI Status Summary
Process completed with exit code 1.
|
|
Frontend Setup 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 2nd, 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 Lint (Ruff)
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-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 Tests (pytest)
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-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Rust Lint (Clippy)
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 2nd, 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 Lint (ESLint)
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 2nd, 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 Type Check (tsc)
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 2nd, 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 Tests (Vitest)
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 2nd, 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 Build (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 2nd, 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/
|
|
Contracts Check (Anchor)
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 2nd, 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/
|