feat(binding-mcp): MCP elicitation across server, proxy, and client kinds (#1739) #7597
jfallowsAnnotations
1 error and 129 warnings
|
testing (grpc.kafka.fanout)
Process completed with exit code 1.
|
|
testing (tls.echo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (tls.echo)
Failed to restore: Cache service responded with 400
|
|
testing (tls.echo)
Failed to restore: Cache service responded with 400
|
|
testing (tcp.echo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (tcp.echo)
Failed to restore: Cache service responded with 400
|
|
testing (tcp.echo)
Failed to restore: Cache service responded with 400
|
|
testing (http.filesystem)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (http.filesystem)
Failed to restore: Cache service responded with 400
|
|
testing (http.filesystem)
Failed to restore: Cache service responded with 400
|
|
testing (http.metrics)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (http.metrics)
Failed to restore: Cache service responded with 400
|
|
testing (http.metrics)
Failed to restore: Cache service responded with 400
|
|
testing (ws.echo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (ws.echo)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0wh4BagAAAADeBnspl4VXS61b+HHYewJBU0xDMzFFREdFMDgxOQBFZGdl
|
|
testing (ws.echo)
Failed to restore: Cache service responded with 400
|
|
testing (ws.echo)
Failed to restore: Cache service responded with 400
|
|
testing (http.json.schema)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (http.json.schema)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0wx4BagAAAAAGvVuFVsZJTKYiojXTec1EU0xDMzFFREdFMDExOABFZGdl
|
|
testing (http.json.schema)
Failed to restore: Cache service responded with 400
|
|
testing (http.json.schema)
Failed to restore: Cache service responded with 400
|
|
testing (http.proxy.jwt)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (http.proxy.jwt)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0xR4BagAAAACOray5T0NfTrOWB2BHjLQIQ0hHRURHRTE3MTkARWRnZQ==
|
|
testing (http.proxy.jwt)
Failed to restore: Cache service responded with 400
|
|
testing (http.proxy.jwt)
Failed to restore: Cache service responded with 400
|
|
testing (grpc.echo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (grpc.echo)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0xB4BagAAAADIZxCMUnlzQIo4Hzma52fjU0xDMzFFREdFMDEyMgBFZGdl
|
|
testing (grpc.echo)
Failed to restore: Cache service responded with 400
|
|
testing (grpc.echo)
Failed to restore: Cache service responded with 400
|
|
testing (tls.reflect)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (tls.reflect)
Failed to restore: Cache service responded with 400
|
|
testing (tls.reflect)
Failed to restore: Cache service responded with 400
|
|
testing (http.proxy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (http.proxy)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0yB4BagAAAABaQijKirZ9S6IgLUp8s+W8U0xDMzFFREdFMDExMwBFZGdl
|
|
testing (http.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (http.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (asyncapi.mqtt.proxy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (asyncapi.mqtt.proxy)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0yR4BagAAAAClMx756VH+S54+oFeUMaqPQ0hJMzBFREdFMDIwOABFZGdl
|
|
testing (asyncapi.mqtt.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (asyncapi.mqtt.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (amqp.reflect)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (amqp.reflect)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0yh4BagAAAADZksbSu2i8RonLt+WuKnidTVNQMzExMDAwMTAxMDM3AEVkZ2U=
|
|
testing (amqp.reflect)
Failed to restore: Cache service responded with 400
|
|
testing (amqp.reflect)
Failed to restore: Cache service responded with 400
|
|
testing (openapi.proxy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (openapi.proxy)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0zR4BagAAAACL6qfvQt4YR6io55kOYpRKU0xDMzFFREdFMDcxMgBFZGdl
|
|
testing (openapi.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (openapi.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (mqtt.proxy.jwt)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (mqtt.proxy.jwt)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0zx4BagAAAADMDpE8w6A+RqjTxmX+O1WRUEhMMzBFREdFMDIwNwBFZGdl
|
|
testing (mqtt.proxy.jwt)
Failed to restore: Cache service responded with 400
|
|
testing (mqtt.proxy.jwt)
Failed to restore: Cache service responded with 400
|
|
testing (grpc.proxy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (grpc.proxy)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0zx4BagAAAAA4E2E3c6M1RZhUSkSBmNqJUEhMMzBFREdFMDQxMABFZGdl
|
|
testing (grpc.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (grpc.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (asyncapi.sse.proxy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (asyncapi.sse.proxy)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>00R4BagAAAADn8CQMO/E6Qbo2Wf5ucAOoU0xDMzFFREdFMDIwOABFZGdl
|
|
testing (asyncapi.sse.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (asyncapi.sse.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (sse.proxy.jwt)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (sse.proxy.jwt)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>00x4BagAAAAAAUspBydcoQIE9WPIqsCkMUEhMMzBFREdFMDExNABFZGdl
|
|
testing (sse.proxy.jwt)
Failed to restore: Cache service responded with 400
|
|
testing (sse.proxy.jwt)
Failed to restore: Cache service responded with 400
|
|
testing (http.kafka.crud)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (http.kafka.crud)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>03B4BagAAAACYhINN/r26Sb7puSO0R4RHQ0hHRURHRTE4MTAARWRnZQ==
|
|
testing (http.kafka.crud)
Failed to restore: Cache service responded with 400
|
|
testing (http.kafka.crud)
Failed to restore: Cache service responded with 400
|
|
testing (http.kafka.proto.oneway)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (http.kafka.proto.oneway)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>03B4BagAAAAAf52eZanmjSr6UBcpOhr44Q0hJMzBFREdFMDMxOQBFZGdl
|
|
testing (http.kafka.proto.oneway)
Failed to restore: Cache service responded with 400
|
|
testing (http.kafka.proto.oneway)
Failed to restore: Cache service responded with 400
|
|
testing (http.kafka.proto.json)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (http.kafka.proto.json)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>03x4BagAAAAApAItYunAkR5owHlABKBFpTVNQMzExMDAwMTA0MDExAEVkZ2U=
|
|
testing (http.kafka.proto.json)
Failed to restore: Cache service responded with 400
|
|
testing (http.kafka.proto.json)
Failed to restore: Cache service responded with 400
|
|
testing (grpc.kafka.fanout)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jwalton/gh-docker-logs@v2, ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (grpc.kafka.fanout)
Failed to restore: Cache service responded with 400
|
|
testing (http.kafka.cache)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (http.kafka.cache)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>04x4BagAAAACT1Ee8OyycS7GkVG4AAhmeU0xDMzFFREdFMDcwOQBFZGdl
|
|
testing (http.kafka.cache)
Failed to restore: Cache service responded with 400
|
|
testing (http.kafka.cache)
Failed to restore: Cache service responded with 400
|
|
testing (http.kafka.sync)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (http.kafka.sync)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>05R4BagAAAABNXDeaxZTEQ7s33IL29hxlUEhMMzBFREdFMDEyMgBFZGdl
|
|
testing (http.kafka.sync)
Failed to restore: Cache service responded with 400
|
|
testing (http.kafka.sync)
Failed to restore: Cache service responded with 400
|
|
testing (http.kafka.async)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (http.kafka.async)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>05R4BagAAAABNfixKL819Q7SQBLV94lPnUEhYMzFFREdFMDUwOABFZGdl
|
|
testing (http.kafka.async)
Failed to restore: Cache service responded with 400
|
|
testing (http.kafka.async)
Failed to restore: Cache service responded with 400
|
|
testing (grpc.kafka.echo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (grpc.kafka.echo)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>05x4BagAAAABtGY79BTxeR6IbKIXO6DBPUEhMMzBFREdFMDIxNgBFZGdl
|
|
testing (grpc.kafka.echo)
Failed to restore: Cache service responded with 400
|
|
testing (grpc.kafka.echo)
Failed to restore: Cache service responded with 400
|
|
testing (http.kafka.oneway)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (http.kafka.oneway)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>06B4BagAAAAAN8FEFeO8ORYglj5aZUN/QU0xDMzFFREdFMDcyMQBFZGdl
|
|
testing (http.kafka.oneway)
Failed to restore: Cache service responded with 400
|
|
testing (http.kafka.oneway)
Failed to restore: Cache service responded with 400
|
|
testing (http.kafka.avro.json)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (http.kafka.avro.json)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>06h4BagAAAABZ9Fp9arGoS6h4pIXSSMWMQ0hHRURHRTE4MDUARWRnZQ==
|
|
testing (http.kafka.avro.json)
Failed to restore: Cache service responded with 400
|
|
testing (http.kafka.avro.json)
Failed to restore: Cache service responded with 400
|
|
testing (sse.kafka.fanout)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (sse.kafka.fanout)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>06x4BagAAAACml0B4mHhURLCoZLKUlaLBUEhMMzBFREdFMDQxMABFZGdl
|
|
testing (sse.kafka.fanout)
Failed to restore: Cache service responded with 400
|
|
testing (sse.kafka.fanout)
Failed to restore: Cache service responded with 400
|
|
testing (openapi.asyncapi.kakfa.proxy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (openapi.asyncapi.kakfa.proxy)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>07R4BagAAAABgPOAXQ+y9TIndPE4zYkg1UEhYMzFFREdFMDUxOABFZGdl
|
|
testing (openapi.asyncapi.kakfa.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (openapi.asyncapi.kakfa.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (mqtt.kafka.proxy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (mqtt.kafka.proxy)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>09x4BagAAAADLmes5wZkSTY2ZsNMQJD7RTEFYRURHRTIwMDcARWRnZQ==
|
|
testing (mqtt.kafka.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (mqtt.kafka.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (sse.kafka.fanout.jwt)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (sse.kafka.fanout.jwt)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0AB8BagAAAAAikh3mfAhCQYp+QM+NGnZgQ0hJMzBFREdFMDIxOABFZGdl
|
|
testing (sse.kafka.fanout.jwt)
Failed to restore: Cache service responded with 400
|
|
testing (sse.kafka.fanout.jwt)
Failed to restore: Cache service responded with 400
|
|
testing (asyncapi.http.kafka.proxy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (asyncapi.http.kafka.proxy)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0AR8BagAAAAAGjuzW2jeDQa0GutvxgJaaTEFYRURHRTE5MDkARWRnZQ==
|
|
testing (asyncapi.http.kafka.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (asyncapi.http.kafka.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (asyncapi.mqtt.kafka.proxy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (asyncapi.mqtt.kafka.proxy)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0CB8BagAAAADVr/mvywpqR4bMaBDXI08ZU0xDMzFFREdFMDExNQBFZGdl
|
|
testing (asyncapi.mqtt.kafka.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (asyncapi.mqtt.kafka.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (asyncapi.sse.kafka.proxy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ScribeMD/docker-cache@0.5.0. 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/
|
|
testing (asyncapi.sse.kafka.proxy)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Cx8BagAAAACNo6zr0G5uSZzec5eHI9d1TEFYRURHRTE2MDcARWRnZQ==
|
|
testing (asyncapi.sse.kafka.proxy)
Failed to restore: Cache service responded with 400
|
|
testing (asyncapi.sse.kafka.proxy)
Failed to restore: Cache service responded with 400
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
grpc.kafka.fanout_logs.tgz
|
10.5 KB |
sha256:202bca5f6ec39a09676578066f1925fc65ee3a922b07a0c37c4e064a3f3b4336
|
|