Skip to content

fix: gracefully handle MCP server failures instead of crashing (#477) #1167

fix: gracefully handle MCP server failures instead of crashing (#477)

fix: gracefully handle MCP server failures instead of crashing (#477) #1167

Triggered via push April 9, 2026 15:58
Status Success
Total duration 1m 11s
Artifacts 1
Build and validate schema package
41s
Build and validate schema package
Publish schema to TestPyPI (best effort)
13s
Publish schema to TestPyPI (best effort)
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Build and validate schema package
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/setup-python@v5, actions/upload-artifact@v4, astral-sh/setup-uv@v6. 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 and validate schema package
The process '/usr/bin/git' failed with exit code 128
Publish schema to TestPyPI (best effort)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/setup-python@v5, astral-sh/setup-uv@v6. 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/
Publish schema to TestPyPI (best effort)
No file matched to [/home/runner/work/idun-agent-platform/idun-agent-platform/**/*requirements*.txt,/home/runner/work/idun-agent-platform/idun-agent-platform/**/*requirements*.in,/home/runner/work/idun-agent-platform/idun-agent-platform/**/*constraints*.txt,/home/runner/work/idun-agent-platform/idun-agent-platform/**/*constraints*.in,/home/runner/work/idun-agent-platform/idun-agent-platform/**/pyproject.toml,/home/runner/work/idun-agent-platform/idun-agent-platform/**/uv.lock,/home/runner/work/idun-agent-platform/idun-agent-platform/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
Publish schema to TestPyPI (best effort)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.

Artifacts

Produced during runtime
Name Size Digest
schema-dist-0.5.2.dev20260409155819 Expired
51.8 KB
sha256:33aadbe9421e2cddb5b3f69716425029587a1775b28a43cbf0971373a2f72455