Skip to content

chore: update submodule akoflow-workflow-engine to latest commit #4

chore: update submodule akoflow-workflow-engine to latest commit

chore: update submodule akoflow-workflow-engine to latest commit #4

Triggered via push April 6, 2026 04:01
Status Failure
Total duration 56s
Artifacts 1

release.yml

on: push
Prepare
3s
Prepare
Matrix: build-desktop
Build Workflow Engine
13s
Build Workflow Engine
Docker — Workflow Engine
8s
Docker — Workflow Engine
Docker — Control Plane
8s
Docker — Control Plane
Docker — Standalone
44s
Docker — Standalone
Create GitHub Release
0s
Create GitHub Release
Fit to window
Zoom out
Zoom in

Annotations

18 errors and 7 warnings
Desktop — Linux (x64)
The process '/usr/bin/git' failed with exit code 128
Desktop — Linux (x64)
Fetched in submodule path 'akoflow-deployment-control-plane', but it did not contain 53951cbca93c6f3da448e19223b02ccacb2abfcd. Direct fetching of that commit failed.
Desktop — Linux (x64)
remote error: upload-pack: not our ref 53951cbca93c6f3da448e19223b02ccacb2abfcd
Docker — Control Plane
The process '/usr/bin/git' failed with exit code 128
Docker — Control Plane
Fetched in submodule path '***-deployment-control-plane', but it did not contain 53951cbca93c6f3da448e19223b02ccacb2abfcd. Direct fetching of that commit failed.
Docker — Control Plane
remote error: upload-pack: not our ref 53951cbca93c6f3da448e19223b02ccacb2abfcd
Docker — Workflow Engine
The process '/usr/bin/git' failed with exit code 128
Docker — Workflow Engine
Fetched in submodule path '***-deployment-control-plane', but it did not contain 53951cbca93c6f3da448e19223b02ccacb2abfcd. Direct fetching of that commit failed.
Docker — Workflow Engine
remote error: upload-pack: not our ref 53951cbca93c6f3da448e19223b02ccacb2abfcd
Desktop — macOS (arm64 + x64)
The process '/opt/homebrew/bin/git' failed with exit code 128
Desktop — macOS (arm64 + x64)
Fetched in submodule path 'akoflow-deployment-control-plane', but it did not contain 53951cbca93c6f3da448e19223b02ccacb2abfcd. Direct fetching of that commit failed.
Desktop — macOS (arm64 + x64)
remote error: upload-pack: not our ref 53951cbca93c6f3da448e19223b02ccacb2abfcd
Build Workflow Engine
The process '/usr/bin/git' failed with exit code 128
Build Workflow Engine
Fetched in submodule path 'akoflow-deployment-control-plane', but it did not contain 53951cbca93c6f3da448e19223b02ccacb2abfcd. Direct fetching of that commit failed.
Build Workflow Engine
remote error: upload-pack: not our ref 53951cbca93c6f3da448e19223b02ccacb2abfcd
Desktop — Windows (x64)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
Desktop — Windows (x64)
Fetched in submodule path 'akoflow-deployment-control-plane', but it did not contain 53951cbca93c6f3da448e19223b02ccacb2abfcd. Direct fetching of that commit failed.
Desktop — Windows (x64)
remote error: upload-pack: not our ref 53951cbca93c6f3da448e19223b02ccacb2abfcd
Desktop — Linux (x64)
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/
Docker — Control Plane
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/
Docker — Workflow Engine
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/
Desktop — macOS (arm64 + x64)
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/
Build Workflow Engine
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/
Desktop — Windows (x64)
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/
Docker — Standalone
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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
UFFeScience~akoflow~VJR4OC.dockerbuild
121 KB
sha256:56427212fd6ec4342cf703dfa9e7723f8ff8814f4dedfce104f9e8e56d73a8fe