Apply client workspace compatibility patches for newer ROS 2 interface packages #144
pr.yml
on: pull_request
CI
/
micro_ros_build
3m 2s
CI
/
micro_ros_agent
2m 35s
Matrix: CI / micro_ros_client
Annotations
26 errors and 25 warnings
|
CI / micro_ros_client (generate_lib, $(pwd)/src/micro_ros_setup/config/generate_lib/generic/demo_toolc...
Process completed with exit code 1.
|
|
CI / micro_ros_client (zephyr, host, ping_pong, -t udp -i 192.168.1.1 -p 8080, firmware/build/zephyr/z...
Process completed with exit code 2.
|
|
CI / micro_ros_client (zephyr, olimex-stm32-e407, int32_publisher, -t serial-usb, firmware/build/zephy...
Process completed with exit code 2.
|
|
CI / micro_ros_client (freertos, nucleo_f446re, int32_publisher, -t serial -d 1, firmware/freertos_app...
Process completed with exit code 2.
|
|
CI / micro_ros_client (zephyr, nucleo_h743zi, int32_publisher, -t serial -d 3, firmware/build/zephyr/z...
Process completed with exit code 2.
|
|
CI / micro_ros_client (zephyr, discovery_l475_iot1, int32_publisher, -t serial-usb, firmware/build/zep...
Process completed with exit code 2.
|
|
|
|
|
|
|
|
CI / micro_ros_client (freertos, nucleo_f767zi, int32_publisher, -t serial -d 1, firmware/freertos_app...
The operation was canceled.
|
|
|
|
CI / micro_ros_client (host, install/micro_ros_demos_rclc/lib/micro_ros_demos_rclc/int32_publisher/int...
The operation was canceled.
|
|
|
|
CI / micro_ros_client (freertos, esp32, int32_publisher, -t serial -d 1, firmware/freertos_apps/micror...
The operation was canceled.
|
|
|
|
CI / micro_ros_client (freertos, nucleo_f746zg, int32_publisher, -t serial -d 1, firmware/freertos_app...
The operation was canceled.
|
|
|
|
CI / micro_ros_client (zephyr, nucleo_f746zg, int32_publisher, -t serial -d 3, firmware/build/zephyr/z...
The operation was canceled.
|
|
CI / micro_ros_agent
The run was canceled by @EugenioCollado.
|
|
|
|
CI / micro_ros_agent
The operation was canceled.
|
|
CI / micro_ros_client (freertos, olimex-stm32-e407, int32_publisher, -t serial -d 1, firmware/freertos...
The operation was canceled.
|
|
|
|
CI / micro_ros_client (freertos, nucleo_f446ze, int32_publisher, -t serial -d 1, firmware/freertos_app...
The operation was canceled.
|
|
Pull Request CI
The run was canceled by @EugenioCollado.
|
|
Pull Request CI
The run was canceled by @EugenioCollado.
|
|
CI / micro_ros_build
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/upload-artifact@v4.4.0, ros-tooling/setup-ros@0.7.13. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
CI / micro_ros_build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
CI / micro_ros_client (generate_lib, $(pwd)/src/micro_ros_setup/config/generate_lib/generic/demo_toolc...
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/download-artifact@v4.1.7, ros-tooling/setup-ros@0.7.13. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
CI / micro_ros_client (generate_lib, $(pwd)/src/micro_ros_setup/config/generate_lib/generic/demo_toolc...
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
CI / micro_ros_client (zephyr, host, ping_pong, -t udp -i 192.168.1.1 -p 8080, firmware/build/zephyr/z...
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/download-artifact@v4.1.7, ros-tooling/setup-ros@0.7.13. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
CI / micro_ros_client (zephyr, host, ping_pong, -t udp -i 192.168.1.1 -p 8080, firmware/build/zephyr/z...
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
CI / micro_ros_client (zephyr, olimex-stm32-e407, int32_publisher, -t serial-usb, firmware/build/zephy...
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/download-artifact@v4.1.7, ros-tooling/setup-ros@0.7.13. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
CI / micro_ros_client (zephyr, olimex-stm32-e407, int32_publisher, -t serial-usb, firmware/build/zephy...
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
CI / micro_ros_client (freertos, nucleo_f446re, int32_publisher, -t serial -d 1, firmware/freertos_app...
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/download-artifact@v4.1.7, ros-tooling/setup-ros@0.7.13. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
CI / micro_ros_client (freertos, nucleo_f446re, int32_publisher, -t serial -d 1, firmware/freertos_app...
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
CI / micro_ros_client (zephyr, nucleo_h743zi, int32_publisher, -t serial -d 3, firmware/build/zephyr/z...
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/download-artifact@v4.1.7, ros-tooling/setup-ros@0.7.13. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
CI / micro_ros_client (zephyr, nucleo_h743zi, int32_publisher, -t serial -d 3, firmware/build/zephyr/z...
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
CI / micro_ros_client (raspbian, buster_v7, agent_lite, firmware/bin/micro_ros_agent_lite)
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/download-artifact@v4.1.7, ros-tooling/setup-ros@0.7.13. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
CI / micro_ros_client (raspbian, buster_v7, agent_lite, firmware/bin/micro_ros_agent_lite)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
CI / micro_ros_client (zephyr, discovery_l475_iot1, int32_publisher, -t serial-usb, firmware/build/zep...
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/download-artifact@v4.1.7, ros-tooling/setup-ros@0.7.13. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
CI / micro_ros_client (zephyr, discovery_l475_iot1, int32_publisher, -t serial-usb, firmware/build/zep...
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
CI / micro_ros_client (freertos, nucleo_f767zi, int32_publisher, -t serial -d 1, firmware/freertos_app...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, ros-tooling/setup-ros@0.7.13. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
CI / micro_ros_client (host, install/micro_ros_demos_rclc/lib/micro_ros_demos_rclc/int32_publisher/int...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, ros-tooling/setup-ros@0.7.13. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
CI / micro_ros_client (freertos, esp32, int32_publisher, -t serial -d 1, firmware/freertos_apps/micror...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, ros-tooling/setup-ros@0.7.13. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
CI / micro_ros_client (freertos, nucleo_f746zg, int32_publisher, -t serial -d 1, firmware/freertos_app...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, ros-tooling/setup-ros@0.7.13. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
CI / micro_ros_client (zephyr, nucleo_f746zg, int32_publisher, -t serial -d 3, firmware/build/zephyr/z...
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/download-artifact@v4.1.7, ros-tooling/setup-ros@0.7.13. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
CI / micro_ros_client (zephyr, nucleo_f746zg, int32_publisher, -t serial -d 3, firmware/build/zephyr/z...
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
CI / micro_ros_agent
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, ros-tooling/setup-ros@0.7.13. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
CI / micro_ros_client (freertos, olimex-stm32-e407, int32_publisher, -t serial -d 1, firmware/freertos...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, ros-tooling/setup-ros@0.7.13. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
CI / micro_ros_client (freertos, nucleo_f446ze, int32_publisher, -t serial -d 1, firmware/freertos_app...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, ros-tooling/setup-ros@0.7.13. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 | |
|---|---|---|---|
|
micro_ros_build_5.0.2-vulcanexus
|
94.4 KB |
sha256:498847ace42df17ad322fc259ccf2851755c98a77a7317ad78ba5f2de6f1b8ea
|
|