Skip to content

Add modelCapabilities override #612

Add modelCapabilities override

Add modelCapabilities override #612

Triggered via pull request April 7, 2026 09:41
Status Failure
Total duration 1m 45s
Artifacts

scenario-builds.yml

on: pull_request
TypeScript scenarios
46s
TypeScript scenarios
Python scenarios
20s
Python scenarios
Go scenarios
17s
Go scenarios
C# scenarios
1m 41s
C# scenarios
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
Go scenarios
Process completed with exit code 1.
Go scenarios
cannot use *resp.Data.Content (variable of struct type copilot.DataContent) as string value in struct literal
Go scenarios
cannot use *resp.Data.Content (variable of struct type copilot.DataContent) as string value in struct literal
Go scenarios
cannot use *response.Data.Content (variable of struct type copilot.DataContent) as string value in struct literal
TypeScript scenarios
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 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/
C# scenarios
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 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/