Skip to content

fix[bug]: handle non-JSON responses and query params in REST tools (#… #6426

fix[bug]: handle non-JSON responses and query params in REST tools (#…

fix[bug]: handle non-JSON responses and query params in REST tools (#… #6426

Triggered via push April 14, 2026 15:19
Status Success
Total duration 52m 2s
Artifacts 9
Matrix: build
Create Manifest
19s
Create Manifest
Sign Images
34s
Sign Images
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Build amd64
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/login-action@c94ce9fb468520275223c153574b00df6fe4bcc9, docker/metadata-action@c299e40c65443455700f0fdfc63efafe5b349051, 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/
Build arm64
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/login-action@c94ce9fb468520275223c153574b00df6fe4bcc9, docker/metadata-action@c299e40c65443455700f0fdfc63efafe5b349051, 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/
Build s390x
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/login-action@c94ce9fb468520275223c153574b00df6fe4bcc9, docker/metadata-action@c299e40c65443455700f0fdfc63efafe5b349051, 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/
Build ppc64le
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/login-action@c94ce9fb468520275223c153574b00df6fe4bcc9, docker/metadata-action@c299e40c65443455700f0fdfc63efafe5b349051, 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/
Create Manifest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@c94ce9fb468520275223c153574b00df6fe4bcc9, 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/
Sign Images
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@c94ce9fb468520275223c153574b00df6fe4bcc9. 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~GIWRBI.dockerbuild
149 KB
sha256:1dfaca0afa5754ab9e82b1bc944f86052d2a0edbc245d878369b7f184b25b940
IBM~mcp-context-forge~RMSIJ4.dockerbuild
142 KB
sha256:fca739dab5309d3dda4d9542e1481023c9e9b607ea1bdd2d64bc143c10844e5e
IBM~mcp-context-forge~T2TN55.dockerbuild
139 KB
sha256:b42b4deff34d44abc362f60c82a53903c74fc460dc7c6b65cc7e6b419410c6ca
IBM~mcp-context-forge~Z0RFP7.dockerbuild
97.6 KB
sha256:fba27b1469f717a6ec2b767270d3b5e861c157660f03d2782a31b453925f6fc8
digest-amd64 Expired
244 Bytes
sha256:56287cf518392257577ce453625222f9929d593c5df369a23a122dcfc8ba9157
digest-arm64 Expired
244 Bytes
sha256:b2254b51b12ab38f578c94187c6e486648e6fa37a88a87d130e662e05e6697eb
digest-ppc64le Expired
244 Bytes
sha256:8a5005c3067e6376ec54c2cc036a294ae07b575b3774e6616491978d1757a64a
digest-s390x Expired
244 Bytes
sha256:ecfa7a4a4a8c1f2cd3c0463717f80c1b33d6358b6a189bfca435b57c65c995f3
ibm-mcp-context-forge_2b6a68ad5f1dc6f4f683bedaea99ec519f2b266c.spdx.json
514 KB
sha256:432fe02b8adf17724256b1a139b21fa92d248bf1ab69bf47ec9e63f6308b030f