Skip to content
PR Build

feat(server-detail): display + edit headers/env, with reveal & convert-to-secret #890

Sign in to view logs

feat(server-detail): display + edit headers/env, with reveal & convert-to-secret

feat(server-detail): display + edit headers/env, with reveal & convert-to-secret #890

Triggered via pull request May 14, 2026 11:29
@DumbrisDumbris
synchronize #466
feat/server-detail-headers-env
Status Success
Total duration 5m 20s
Artifacts 9

pr-build.yml

on: pull_request
Prepare Version
11s
Prepare Version
Verify OpenAPI Artifacts
12s
Verify OpenAPI Artifacts
Build Frontend
30s
Build Frontend
Matrix: Build Binaries
Fit to window
Zoom out
Zoom in

Annotations

9 warnings and 2 notices
Prepare Version
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/
Verify OpenAPI Artifacts
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-go@v5. 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 Frontend
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-node@v4, actions/upload-artifact@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/
Build Binaries (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/upload-artifact@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/
Build Binaries (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/upload-artifact@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/
Build Binaries (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/upload-artifact@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/
Build Binaries (macos-15, 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/upload-artifact@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/
Build Binaries (macos-15, 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/upload-artifact@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/
Build Binaries (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/upload-artifact@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/
Build Binaries (windows-latest, windows, arm64, 1, mcpproxy-windows-arm64.exe, zip)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Build Binaries (windows-latest, windows, amd64, 1, mcpproxy-windows-amd64.exe, zip)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

Artifacts

Produced during runtime
Name Size Digest
archive-darwin-amd64 Expired
26.4 MB
sha256:86bd8a0cca981e7de458bbfa3f52b3c4751522c28d30f71470357483a62952fc
archive-darwin-arm64 Expired
23.8 MB
sha256:7a2129539f6ac75666ac5959ba028ac14c5ce441c85208a8b0d934145839e682
archive-linux-amd64 Expired
15.4 MB
sha256:c934d5763714a61d247ab79f7496cf3cb57a6da01823c3f2af3bb0850ee600e8
archive-linux-arm64 Expired
13.8 MB
sha256:e0f47d6622c77ab9af7d906563e256be22ab653fc620c7e911d02597934a68d0
archive-windows-amd64 Expired
26.2 MB
sha256:8ed55f734bfaedd7657c7cd9919941c31be85b54b5b449c625cd8557aa168ef8
archive-windows-arm64 Expired
23.3 MB
sha256:9e9ae8449ff400620ed58a0f6d484f4c28a5cbaf59771e666fb3545c344e4b59
frontend-dist-pr Expired
276 KB
sha256:7bd22314b28cf17f0e1228de4d4927bdc1c438759615a74e2b8678f23db231ba
installer-dmg-darwin-amd64 Expired
20.1 MB
sha256:066f703df1b275644854e7670a68703a95ac085c57b627c99c4ad70cbb17b84e
installer-dmg-darwin-arm64 Expired
18.2 MB
sha256:9b49a0458619e479316e755c13ac3e7a5fed42f59cc497955db01d13039de531