Skip to content

feat!: replace Pyro4/ZMQ transport with gRPC #977

feat!: replace Pyro4/ZMQ transport with gRPC

feat!: replace Pyro4/ZMQ transport with gRPC #977

Triggered via pull request March 16, 2026 21:55
Status Failure
Total duration 5m 19s
Artifacts

main.yml

on: pull_request
Check code for issues
3m 51s
Check code for issues
Build kas/ci targets
5m 16s
Build kas/ci targets
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
Check code for issues
Process completed with exit code 1.
Build kas/ci targets
Process completed with exit code 2.
Check code for issues
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. 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 kas/ci targets
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 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/