Skip to content
CI Main Branch

fix(adf): opencode run subcommand, model flag, resource limits, compo… #462

Sign in to view logs

fix(adf): opencode run subcommand, model flag, resource limits, compo…

fix(adf): opencode run subcommand, model flag, resource limits, compo… #462

Triggered via push March 27, 2026 09:49
@AlexMikhalevAlexMikhalev
pushed bd5c0c7
main
Status Failure
Total duration 16m 35s
Artifacts 2

ci-main.yml

on: push
Build Setup
10s
Build Setup
Frontend Build
2m 7s
Frontend Build
WASM Build
29s
WASM Build
Security Scan
8s
Security Scan
Matrix: rust-build
Integration Tests
0s
Integration Tests
Docker Build
0s
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 101.
Rust Build (x86_64-unknown-linux-gnu)
Process completed with exit code 101.
Build Summary
Process completed with exit code 1.
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. 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
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. 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 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. 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/

Artifacts

Produced during runtime
Name Size Digest
frontend-dist
2.67 MB
sha256:b85aa0e719eed4a60d1e5b57afe4055bcef828c7b268d3058e019d14b4a6da8b
wasm-package
135 KB
sha256:00eb65393f80aea6dfc0fa2925ec4e5fa9fc03b2045abd11de3b93d6e1eaec10