Skip to content
PR Build

fix(security): make scan report latency independent of scan history (MCP-2205) #1217

Sign in to view logs

fix(security): make scan report latency independent of scan history (MCP-2205)

fix(security): make scan report latency independent of scan history (MCP-2205) #1217

Triggered via pull request June 14, 2026 04:05
@DumbrisDumbris
opened #655
fix/mcp-2205-scan-report-latency
Status Success
Total duration 7m 10s
Artifacts 9

pr-build.yml

on: pull_request
Prepare Version
13s
Prepare Version
Verify OpenAPI Artifacts
31s
Verify OpenAPI Artifacts
Build Frontend
20s
Build Frontend
Matrix: Build Binaries
Fit to window
Zoom out
Zoom in

Annotations

8 warnings and 2 notices
Build Frontend
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. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Build Binaries (windows-latest, windows, amd64, 1, mcpproxy-windows-amd64.exe, zip)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

Artifacts

Produced during runtime
Name Size Digest
archive-darwin-amd64
28.3 MB
sha256:19ff9ac8df69e9f32f031bd5cdd0335aa980de34acd288de5bcbc9d987ce8ae1
archive-darwin-arm64
25.4 MB
sha256:686e173c384dfa899381ae2ee09511eb2650e4dd209d3111b97f711af03c9b95
archive-linux-amd64
16.4 MB
sha256:d303c4c6283dfc45c32c3ac2b7cf862bdd0bc6c2599f436a0f9515a7812bd2be
archive-linux-arm64
14.7 MB
sha256:ad1822ccb99ec0a8525a5b394727fc9dfedf0cce40f98197d3c4e397d7b3ce53
archive-windows-amd64
28.1 MB
sha256:3779edac905e558bc2aaa4c1503607ee5ae3f6c55e02677f3c04e0e4201fff04
archive-windows-arm64
25 MB
sha256:073eefee72cb7e4b7d55ee9a8db11d34ada5bc1cf66398832edd5df57fa776f4
frontend-dist-pr Expired
316 KB
sha256:54e7a004a89d0b03900ba662174a3a6c6c974c4f73b7bb72adc1c6e34df7f7a8
installer-dmg-darwin-amd64
21.6 MB
sha256:5f1087244e302b560f5dc0d63ec22db043855df1954c2b0902d4a8c74af2ac50
installer-dmg-darwin-arm64
19.6 MB
sha256:b094d4afcbe740f4c0a26d1c3a6636ad5cf3efed05860bea29a3ab18f748cc00