Skip to content

fix: emit model aliases under apiProxy.models instead of top-level config.models #3268

fix: emit model aliases under apiProxy.models instead of top-level config.models

fix: emit model aliases under apiProxy.models instead of top-level config.models #3268

Re-run triggered May 5, 2026 15:49
Status Cancelled
Total duration 1m 14s
Artifacts 1

cgo.yml

on: pull_request
Matrix: cross-platform-build
Matrix: fuzz
Matrix: security-scan
build
5s
build
build-wasm
1m 1s
build-wasm
validate-yaml
13s
validate-yaml
bench
bench
Check validator file sizes
10s
Check validator file sizes
lint-go
52s
lint-go
actions-build
5s
actions-build
security
1m 4s
security
mcp-server-compile-test
5s
mcp-server-compile-test
Alpine Container Test
5s
Alpine Container Test
safe-outputs-conformance
18s
safe-outputs-conformance
canary-go
0s
canary-go
Notify on CGO Failure
0s
Notify on CGO Failure
Fit to window
Zoom out
Zoom in

Annotations

15 errors, 5 warnings, and 1 notice
Alpine Container Test
Canceling since a higher priority waiting request for ci-refs/pull/30367/merge-alpine-container exists
actions-build
Canceling since a higher priority waiting request for ci-refs/pull/30367/merge-actions-build exists
build
Canceling since a higher priority waiting request for ci-refs/pull/30367/merge-build exists
test
Canceling since a higher priority waiting request for ci-refs/pull/30367/merge-test exists
mcp-server-compile-test
Canceling since a higher priority waiting request for ci-refs/pull/30367/merge-mcp-server-compile-test exists
lint-go
Canceling since a higher priority waiting request for ci-refs/pull/30367/merge-lint-go exists
lint-go
The operation was canceled.
Build & Test on macos-latest
Canceling since a higher priority waiting request for ci-refs/pull/30367/merge-cross-platform-macos-latest exists
Build & Test on macos-latest
The operation was canceled.
build-wasm
Canceling since a higher priority waiting request for ci-refs/pull/30367/merge-build-wasm exists
build-wasm
The operation was canceled.
Build & Test on windows-latest
Canceling since a higher priority waiting request for ci-refs/pull/30367/merge-cross-platform-windows-latest exists
Build & Test on windows-latest
The operation was canceled.
security
Canceling since a higher priority waiting request for ci-refs/pull/30367/merge-security exists
security
The operation was canceled.
safe-outputs-conformance
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 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 & Test on macos-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c. 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-wasm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c. 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 & Test on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c. 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/
security
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c. 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 & Test on windows-latest
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

Artifacts

Produced during runtime
Name Size Digest
safe-outputs-conformance-report
1.69 KB
sha256:1a7284fe1229c7a5e35280b349e00cf96915f1747590be92d7345eaa638a412f