Skip to content

fix(ci): use official protoc release with bundled well-known types #2

fix(ci): use official protoc release with bundled well-known types

fix(ci): use official protoc release with bundled well-known types #2

Triggered via push March 23, 2026 20:59
Status Failure
Total duration 5m 47s
Artifacts 2

release-fork.yml

on: push
Build CLI (linux-amd64)
3m 19s
Build CLI (linux-amd64)
Build gateway Docker image
5m 34s
Build gateway Docker image
Create GitHub Release
7s
Create GitHub Release
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
Build gateway Docker image
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c . cross-build.sh && cargo_cross_build --release -p openshell-server -p openshell-sandbox" did not complete successfully: exit code: 101
Build CLI (linux-amd64)
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/upload-artifact@v4, arduino/setup-protoc@v3. 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/
Create GitHub Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, softprops/action-gh-release@v2. 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/
Build gateway Docker image
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. 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
htekdev~OpenShell~IUXMCZ.dockerbuild
61.5 KB
sha256:e34afc47152f051390d7da26f755acb0720cd7e1784b527e836d250a40c91fa7
openshell-linux-amd64
5.92 MB
sha256:32406dabf0cd88f43b551d46d8b94376b7289b9baaefecd867c9e3400ee31d04