Skip to content

feat: add Rust A2A 1.0 runtime support #5903

feat: add Rust A2A 1.0 runtime support

feat: add Rust A2A 1.0 runtime support #5903

Triggered via pull request April 15, 2026 10:25
@lucarliglucarlig
synchronize #3704
a2a-rust
Status Failure
Total duration 5m 40s
Artifacts 3

docker-scan.yml

on: pull_request
Security Scan
2m 8s
Security Scan
Rust-enabled container smoke
5m 34s
Rust-enabled container smoke
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
Rust-enabled container smoke
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/bash -o pipefail -c if [ \"$ENABLE_RUST\" = \"true\" ]; then cargo build --release -p contextforge_a2a_runtime && cp /build/target/release/contextforge_a2a_runtime /build/target/release/contextforge-a2a-runtime && echo \"✅ Rust A2A runtime built successfully\"; else echo \"⏭️ Skipping Rust A2A runtime build\"; fi" did not complete successfully: exit code: 1
Security Scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, docker/build-push-action@10e90e3645eae34f1e60eeb005ba3a3d33f178e8, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
Security Scan
Retention days cannot be greater than the maximum allowed retention set within the repository. Using 10 instead.
Rust-enabled container smoke
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@10e90e3645eae34f1e60eeb005ba3a3d33f178e8, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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
IBM~mcp-context-forge~IW38CI.dockerbuild
51.9 KB
sha256:dc4c62ea0b8c309ecbfcaf64732ab7e3a56e29ba228fe359db845b7d7473d80a
IBM~mcp-context-forge~O7XT3Y.dockerbuild
97.1 KB
sha256:e2ef5ae29318b432bd71890580cb4965d347dbecd7abbae8aa985049e2c384fa
sbom
513 KB
sha256:16860913f06cddb1c719ecb573840a6fc0b202c69bf8baf167ea104d66f71156