Skip to content

Restore accidently deleted RPC code #1263

Restore accidently deleted RPC code

Restore accidently deleted RPC code #1263

Triggered via pull request April 24, 2026 22:00
@rovo89rovo89
synchronize #282
fix/rpc-init
Status Success
Total duration 6m 27s
Artifacts 8

build-image.yaml

on: pull_request
Matrix: build
Matrix: merge
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build (ubuntu-24.04-arm, arm64, default, ./docker/Dockerfile)
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/setup-python@v5, actions/upload-artifact@v4, docker/build-push-action@v6, docker/metadata-action@v5, docker/setup-buildx-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/
build (ubuntu-24.04, amd64, default, ./docker/Dockerfile)
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/setup-python@v5, actions/upload-artifact@v4, docker/build-push-action@v6, docker/metadata-action@v5, docker/setup-buildx-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/
build (ubuntu-24.04, amd64, legacy, ./docker/Dockerfile.Legacy)
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/setup-python@v5, actions/upload-artifact@v4, docker/build-push-action@v6, docker/metadata-action@v5, docker/setup-buildx-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/
build (ubuntu-24.04-arm, arm64, legacy, ./docker/Dockerfile.Legacy)
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/setup-python@v5, actions/upload-artifact@v4, docker/build-push-action@v6, docker/metadata-action@v5, docker/setup-buildx-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
ClemensElflein~open_mower_ros~0UATB7.dockerbuild
87 KB
sha256:84ff9b769363ecec90ab2027feda009dab07e2149731c1731ba03a788092d278
ClemensElflein~open_mower_ros~3HNGWM.dockerbuild
79.9 KB
sha256:4b98c649bfa02107ce5c5d52d0e04e59551153ee9ed2640dfd1db23857e9b133
ClemensElflein~open_mower_ros~JXZ42G.dockerbuild
83 KB
sha256:10b4c2865cfebcda76f7ffdd6023158e8eabf32c358dba6c63b5aa573c69e041
ClemensElflein~open_mower_ros~W045PA.dockerbuild
88.5 KB
sha256:14c73ceebaabdc0bec91454bd081b05c1fa0084d13fdc7afed70414083645f28
digests-amd64-default Expired
244 Bytes
sha256:ec2d1a4f47b4a90e33238f4883dc592e8735bfa5bb7c1299e7affe656d2d2f45
digests-amd64-legacy Expired
244 Bytes
sha256:def966afac892a8df7776acc35d812065610abd6bcbf57606289ae3050f823b7
digests-arm64-default Expired
244 Bytes
sha256:797c9a8c26b56c0c321ff06d2c7bacc09c3602cb98f26aee6fcb87dac4337148
digests-arm64-legacy Expired
244 Bytes
sha256:76261631ba8368f2133a98938e6fa1f6e2451ad11979a27f3213fa513e2161cc