Skip to content
CI Main Branch

fix(symphony): use token-embedded clone URL and increase hook timeout #406

Sign in to view logs

fix(symphony): use token-embedded clone URL and increase hook timeout

fix(symphony): use token-embedded clone URL and increase hook timeout #406

Triggered via push March 14, 2026 13:21
@AlexMikhalevAlexMikhalev
pushed 7eedf4d
main
Status Failure
Total duration 37m 53s
Artifacts 2

ci-main.yml

on: push
Build Setup
9s
Build Setup
Frontend Build
2m 54s
Frontend Build
WASM Build
27s
WASM Build
Security Scan
12s
Security Scan
Matrix: rust-build
Integration Tests
Integration Tests
Docker Build
Docker Build
Build Summary
4s
Build Summary
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
Security Scan
Process completed with exit code 1.
Rust Build (x86_64-unknown-linux-gnu)
Process completed with exit code 101.
Build Summary
Process completed with exit code 1.
Frontend Build
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/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
WASM Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, jetli/wasm-pack-action@v0.4.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 Build (x86_64-unknown-linux-gnu)
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/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Artifacts

Produced during runtime
Name Size Digest
frontend-dist Expired
2.7 MB
sha256:64aadc8c669582d23b2365d7ef190391f58e9a73e6f98867046bc1a7d846a3c2
wasm-package Expired
134 KB
sha256:a038a79d09aac8d48d59c8f4f44f2c15744baeb6f45e0c10f67ed41d18e66e2a