Skip to content

Merge pull request #343 from smart-mcp-proxy/fix/tool-quarantine-anno… #176

Merge pull request #343 from smart-mcp-proxy/fix/tool-quarantine-anno…

Merge pull request #343 from smart-mcp-proxy/fix/tool-quarantine-anno… #176

Triggered via push March 20, 2026 14:28
Status Failure
Total duration 5m 37s
Artifacts 11

release.yml

on: push
Matrix: build
generate-notes
16s
generate-notes
Matrix: sign-windows
build-docker
0s
build-docker
release
release
deploy-docs
deploy-docs
trigger-marketing-update
trigger-marketing-update
Publish to MCP Registry
Publish to MCP Registry
update-homebrew
update-homebrew
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 8 warnings
build (ubuntu-latest, linux, arm64, 0, mcpproxy-linux-arm64, tar.gz)
Unable to download artifact(s): Artifact not found for name: release-notes Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
build (windows-latest, windows, arm64, 1, mcpproxy-windows-arm64.exe, zip)
Unable to download artifact(s): Artifact not found for name: release-notes Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
build (macos-14, darwin, arm64, 1, mcpproxy-darwin-arm64, tar.gz)
Process completed with exit code 1.
build (macos-14, darwin, amd64, 1, mcpproxy-darwin-amd64, tar.gz)
The strategy configuration was canceled because "build.macos-14_darwin_arm64_1_m" failed
build (macos-14, darwin, amd64, 1, mcpproxy-darwin-amd64, tar.gz)
The operation was canceled.
build (macos-14, darwin, amd64, 1, mcpproxy-darwin-amd64, tar.gz)
Cannot open: File exists
build (macos-14, darwin, amd64, 1, mcpproxy-darwin-amd64, tar.gz)
Cannot open: File exists
build (macos-14, darwin, amd64, 1, mcpproxy-darwin-amd64, tar.gz)
Cannot open: File exists
build (macos-14, darwin, amd64, 1, mcpproxy-darwin-amd64, tar.gz)
Cannot open: File exists
build (macos-14, darwin, amd64, 1, mcpproxy-darwin-amd64, tar.gz)
Cannot open: File exists
build (macos-14, darwin, amd64, 1, mcpproxy-darwin-amd64, tar.gz)
Cannot open: File exists
build (macos-14, darwin, amd64, 1, mcpproxy-darwin-amd64, tar.gz)
Cannot open: File exists
build (macos-14, darwin, amd64, 1, mcpproxy-darwin-amd64, tar.gz)
Cannot open: File exists
build (macos-14, darwin, amd64, 1, mcpproxy-darwin-amd64, tar.gz)
Cannot open: File exists
build (macos-14, darwin, amd64, 1, mcpproxy-darwin-amd64, tar.gz)
Cannot open: File exists
generate-notes
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 (ubuntu-latest, linux, arm64, 0, mcpproxy-linux-arm64, tar.gz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-go@v5, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 (ubuntu-latest, linux, amd64, 0, mcpproxy-linux-amd64, tar.gz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-go@v5, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 (windows-latest, windows, arm64, 1, mcpproxy-windows-arm64.exe, zip)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-go@v5, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 (windows-latest, windows, amd64, 1, mcpproxy-windows-amd64.exe, zip)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-go@v5, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 (macos-14, darwin, arm64, 1, mcpproxy-darwin-arm64, tar.gz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-go@v5, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 (macos-14, darwin, amd64, 1, mcpproxy-darwin-amd64, tar.gz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-go@v5, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 (macos-14, darwin, amd64, 1, mcpproxy-darwin-amd64, tar.gz)
Failed to restore: "/opt/homebrew/bin/gtar" failed with error: The process '/opt/homebrew/bin/gtar' failed with exit code 2

Artifacts

Produced during runtime
Name Size Digest
latest-personal-linux-amd64
14.8 MB
sha256:d73248349b582597befe94d4aadc55b1ae71725ff650aab86a8c463a678e25ff
latest-personal-linux-arm64
13.4 MB
sha256:95e4ea4f2f791d0178d71f5031b6dea30b4d4fd1403832b00e79d81bdd8a68b1
latest-personal-windows-amd64
25.6 MB
sha256:69ac4285886f8c300884bd573186c927ec9eed15c803fa0a3187ddcda0895fdc
latest-personal-windows-arm64
22.8 MB
sha256:aa16ad723a6f807d3d4180663444b7cbe99274f3666a73ccd02ddb1063994133
release-notes
752 Bytes
sha256:87227ae229c1745d535456a26756a635f7b9863a850f712893c0c1c5b3d9fc53
unsigned-installer-windows-amd64
19.5 MB
sha256:2c31dc1c37efd1334a03279caac4849f3ed862f9934d1625dbf76332541fdf4c
unsigned-installer-windows-arm64
17.3 MB
sha256:ed069f3678388d7f92afd4dda1a90f000d5e4963ebbb6507b421ece95fc112bc
versioned-personal-linux-amd64
29.7 MB
sha256:1f3684c6f7515934898ac64e5d38c264df92dce4a7d872482f1e81b7f9c58942
versioned-personal-linux-arm64
26.7 MB
sha256:6f842254a98c05bc00e0348af54c534c5bd24794e67d98b86eae6ea02253cdf7
versioned-personal-windows-amd64
51.3 MB
sha256:7fe5a73ac507a027010d6ad5270e953b438401cfb326918e54d4c20daa47fefa
versioned-personal-windows-arm64
45.7 MB
sha256:7f2e9ec8f967a8fb42f67b6076cd81c35e0697e945a9d33409c00e8db86d02d4