Skip to content

Type resolver experiement #154

Type resolver experiement

Type resolver experiement #154

Triggered via pull request May 15, 2026 16:56
Status Failure
Total duration 4m 13s
Artifacts

python-integration.yml

on: pull_request
Build & Regenerate
1m 31s
Build & Regenerate
Mock API Tests
0s
Mock API Tests
Type Checking
0s
Type Checking
Lint & Format
0s
Lint & Format
Docs Validation
0s
Docs Validation
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 1 warning
Build & Regenerate
Process completed with exit code 2.
Build & Regenerate
@typespec/compiler#build: command (/home/runner/work/typespec/typespec/core/packages/compiler) /home/runner/setup-pnpm/node_modules/.bin/pnpm run build exited (2)
Build & Regenerate
Property 'cycle' does not exist on type 'ResolutionResult'.
Build & Regenerate
Implicit conversion of a 'symbol' to a 'string' will fail at runtime. Consider wrapping this expression in 'String(...)'.
Build & Regenerate
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v2. 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/