Skip to content

feat(mcp)!: drop Jinja2 markdown templates — JSON-only ToolResult #134

feat(mcp)!: drop Jinja2 markdown templates — JSON-only ToolResult

feat(mcp)!: drop Jinja2 markdown templates — JSON-only ToolResult #134

Triggered via push May 15, 2026 14:52
Status Failure
Total duration 3m 36s
Artifacts

release.yml

on: push
Publish Client to PyPI
Publish Client to PyPI
Build MCPB bundle
0s
Build MCPB bundle
Publish MCP Server to PyPI
0s
Publish MCP Server to PyPI
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 3 warnings
release-client
The process '/usr/bin/git' failed with exit code 128
release-client
could not read Username for 'https://github.com': terminal prompts disabled
release-client
could not read Username for 'https://github.com': terminal prompts disabled
release-client
could not read Username for 'https://github.com': terminal prompts disabled
release-mcp
The process '/usr/bin/git' failed with exit code 128
release-mcp
could not read Username for 'https://github.com': terminal prompts disabled
release-mcp
could not read Username for 'https://github.com': terminal prompts disabled
release-mcp
could not read Username for 'https://github.com': terminal prompts disabled
test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, astral-sh/setup-uv@v4. 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/
release-client
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. 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/
release-mcp
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. 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/